Onlive Soft > Make-A-Flake

Blog

Getting Began¶

To get began writing a Flake8 plugin you first want:

  • An thought for a plugin

  • An out there bundle title on PyPI

  • A number of variations of Python put in

  • A textual content editor or IDE of some sort

  • An thought of what sort of plugin you wish to construct:

    • Formatter

    • Examine

When you’ve gathered this stuff, you may get began.

All plugins for Flake8 should be registered by way of entry points. On this part we cowl:

  • Easy methods to register your plugin so Flake8 can discover it

  • Easy methods to make Flake8 present your examine plugin with info (by way of command-line flags, operate/class parameters, and so forth.)

  • Easy methods to make a formatter plugin

  • Easy methods to write your examine plugin in order that it really works with Flake8 2.x and three.x

Video

What are Nix flakes?

Flakes are self-contained models which have inputs (dependencies) and outputs (packages, deployment directions, Nix features to be used in different flakes). You possibly can take into consideration them as Rust crates or Go modules however language-independent. Flakes have nice reproducibility as a result of they’re solely allowed to depend upon their inputs and so they pin the precise variations of mentioned inputs in a lockfile.

When you’re already acquainted with Nix, flakes are to Nix expressions what derivations are to construct directions.

Optionally available: nix-direnv .envrc

With the intention to hook into nix-direnv:

Then git add .envrc.

Earlier than we do a full correct construct, we have to populate the Cargo.lock! (Skip this you probably have one!)

When you didn’t decide to make use of nix-direnv, now it is advisable to name nix develop . to enter the total growth shell.

At this level you may check out cargo construct and different related instructions. They need to work and use the libraries and instruments offered by Nix.

Go forward and check a construct:

Get hassle? Attempt operating nix construct --print-build-logs --keep-failed to have the ability to see logs and examine the workdir.

Here is it working:

So how does this do on different crates? I check these recordsdata to a number of different common Rust packages, here is what I wanted to vary for every:

ripgrep

I needed to set mainProgram inside the meta of default.nix:

backside

I additionally needed to set mainProgram to btm. I additionally needed to set doCheck = true in default.nix, because the checks relied on floating atmosphere variables the construct did not have.

Tags