VS Code right-click to analyze
D
David Apirian
This could also be used for explicitly linting trunk ignored or git ignored files. On the command line you can do that with
--force
but there's currently no way to from vscodeD
David Apirian
Hey there, thanks for the request! Could you elaborate on your use case for this? By default we lint every file you open in vscode (if it's in your git repo and not ignored), as well as every file modified (according to git), so you shouldn't have to do anything to lint a file. But maybe you'd want to do this on a folder in the file explorer instead of opening each file in the folder?
Trailstrider
David Apirian: Doesn't seem thats how things are working at the moment. Setup is way more complicated than it should be. Seems like the hold-the-line approach is getting in the way... It goes too far to start. I had another suggestion to have something to help devs be more involved in the "jello setting" process. But even once you have a hold-the-line configuration in place, there are still times you want to see what is coming up, and work on a few of the older checks....
D
David Apirian
Trailstrider: there's no configuration to set up hold the line, and we show both new and preexisting issues, so I'm not sure what you mean. If you have a sec, hop on https://slack.trunk.io to chat - thanks!