4 ms·
I've been working on a general repository linter. The idea is to declaratively define a set of rules/conventions for your repo, (for things that language-specif
by aleqs 20d ago
I've been working on a general repository linter. The idea is to declaratively define a set of rules/conventions for your repo, (for things that language-specific linters don't cover), covering things from directory structure, required files, file staleness/freshness, file size, rules for binary files, rules around use of invisible Unicode, etc. - which can be checked deterministically. Many/most large repos have a set of hand-authored scripts for doing these kinds of checks, the tool I'm building basically packages these in a fast, reusable and extensible tool, with some niceties added.
https://alint.org/ https://alint.org/
https://alint.org/blog/why-alint/ https://alint.org/blog/why-alint/
- jjordan 20d agoIt would be great if I could integrate this into our existing (and rather extensive) eslint config as as a plugin of some sort rather than integrate yet another new tool to our dev environment. Any plans for that?
- aleqs 20d agoYes, this is on the right roadmap, and going to be prioritized now that someone has a real use case. Thanks!