Target for development-assistance tools (hlint, weeder,…)

Here is a routine which I go through all too often.

« Is there a way to do X?

• Oh! Yes, there is a tool for that… uh… So, you stack install weeder and then you uh. And then you… uh… well, it's a bit complicated. » (the real reason why it's complicated is that I just never remember what to do, if I ever did for that particular tool)

It would be really useful if my project management tool, in this case Bazel, could do something sensible out of the box with such tools.

The way I imagine it is supplementary targets for a number of such tools in the same style as the lint rules which are used to check warning compliance. But that would install the extra tool (maybe using rules_nixpkgs) and run it on our code.

But maybe there is another way. It would be cool if I could populate my repo with sensible default configurations for the tool, but this is probably not something Bazel is particularly well-equipped to do.

So, here is a list of tools that can be considered (propose your own, I'll add them to the list!)

• hlint
• weeder

(this is probably related to #33)

Start by reviewing related issue #33 and the current lint-rule approach in rules_haskell. Compare the proposed Bazel targets for hlint and weeder, including installation via rules_nixpkgs and default configurations. Done means the project has an agreed, usable integration approach for these development-assistance tools.