Run in repos without a trunk.yaml
This has come up in a few contexts: * polyrepo setups where folks want just a single trunk.yaml across all of them * folks who want a low-overhead setup for personal development If this is you, please comment describing your use case so that if/when we get around to this, we can consider it when designing the implementation!
hide linter configs
Trunk has a lot of great built-in configs that we suggest to users. Unfortunately, this still requires users to commit those configs into their repo at the root of the repo. In theory, since trunk controls how linters are invoked, it's possible to push those config files into .trunk or instantiate with defaults. We've had two instances of users asking for this: https://trunkcommunity.slack.com/archives/C0205B2FPE3/p1646949401394559 https://trunkcommunity.slack.com/archives/C0205B2FPE3/p1649711092029619
BUG: VS Code prettier on trunk.yaml
Please see the gif... 2 issues I see: 1) The default format isn't good enough? 2) using the prettier run from the problem window causes it to eat the first line every time its run...
VS Code right-click to analyze
Make it possible to do on-demand linting with a right click from file selections in explorer as well as the source editor.
VS Code init and "jello setting" opportunity
It would be nice to be able to use VS Code's extension to do the init and make it possible to fix problems before firming up what to ignore for future hold-the-line checking.
Support equivalent checker ID mappings
Running multiple linters for the same language is usually a good idea on the basis that they cover different things. There is almost ALWAYS overlap on the good ones though.. It would be handy to be able to map equivalent checkers (community supported effort, or with the developers of the linters involved?) The purpose of the mapping of course would be for simpler reference in // trunk-ignore comments, and anywhere else they were needed in the configs... Otherwise we could wind up with large blocks of ignores that could be simplified for code readability. Bonus trick: make it possible to toggle to the original multi-id syntax, as well as to learn potential mappings (w/ human validation in-loop).
Custom linters repo/registry
I found it pretty easy to create a custom linter: https://gist.github.com/metafeather/cd185324f4b646cdd87b47f243fd2e1e I can see already that you get (and will continue to get) asked to support xyz linters forever, but most could probably be handled by the community, if there was somewhere to put and discover them. A well documented example that converts output the LSP format would be a great help (I didn't have time to work that out myself)