🎉 Trunk is in beta. We'd appreciate your feedback - stop by the Trunk Community Slack and let us know what you think. Thanks!
Here are some simple and ultra-clean default configs for linters, formatters, and more. Every character has been scrutinized to create the finest dotfiles in the galaxy. Enjoy 😎
PRs are welcome!
Nobody wants to hear about every missing space as a separate lint error. Don't run prettier via eslint. Don't run flake8 formatting errors instead of autoformatting with black, etc. The same theme rings true with most language linter setups.
Sure, you can embed your eslint settings in package.json or your flake8 settings in setup.cfg,
but please don't. It's just good separation of concerns. It's easy for other people to find the
config options in standalone files, if you stop using a linter it's easy to delete the config, it's
easy to look up the format of a config or get editor autocompletion (they often have schemas on
schemastore.org), everything is easier.
Whether you have a monorepo with language subdirectories or a microrepo with a single source file, by sticking all of your lint configuration at the root, no matter where someone adds new files, they're covered. All too often, large swaths of a codebase go unlinted because linter configs didn't cover some directories.
An ounce of prevention is worth a pound of cure. Running more well configured linters will reduce your bugs, increase consistency, reduce security vulnerabilities, and increase your overall speed. Spend a little time now, reap the rewards forever.
Always have a .editorconfig file, not only for users of your repo using editors, but also some
linters use the settings in .editorconfig. For example shfmt uses it to figure out indentation,
and prettier will also respect it as a fallback to its own config (though that is undocumented).
Clang-format can format a bunch of languages, but we prefer prettier on languages they both cover.
To lint additional languages, you need a section for that language as is shown in this
.clang-format. Note there's a section for proto: Clang-format can autoformat proto files too!
Cool.
This config is yaml, but it's kind of multiple yaml files stacked into the same file. Bad config design, but a good tool!
We turned off all the formatting categories because black handles autoformatting. No one should be hearing about formatting issues one space at a time. This is a theme across many linters.
Black itself has a black-compatible flake8 config here, however it keeps flake8 formatting errors on. If you've autoformatted with black, you won't have any flake8 errors with their config, but really you should be gating your CI on both black and flake8 (with trunk), and it's much nicer to hear that you just need to autoformat your file with black, not hear about every missing space as a different lint error.
Clang-tidy has one of the more annoying configs around. Tidy has ~50 rules which are aliases of other rules. If you don't disable them, you end up getting duplicate results and tidy takes longer.
Also, the config is yaml, but the Checks key takes a string which is a comma separated list
instead of a yaml list. :( The comment blocks at the top describe what we've turned on/off and why.
We turned off all formatting categories which are handled by prettier. If you use trunk](https://trunk.io/), you'll just see that your file needs to be autoformatted, not every instance of missing whitespace in your markdown.
This config turns on as much as possible, but relies on sourcing other scripts always relative to
the current script's directory. If you want to turn off checking related to source, you could add:
disable=SC1090
disable=SC1091
Trunk 🎉 (docs • vscode extension • github action)
Think there's a better setup for one of these linters? Put up a PR and let's see it! Also happy to see contributions for linters we haven't covered here.