Replies: 1 comment
-
Another advantage of LSP aside from expanding languages may be performance. For example pyright Of course this is a tradeoff with hermeticity, the same as persistent workers for compilation under Bazel, very easy for them to get stateful and have bugs like passing when they should fail after removing an input. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
What is the current behavior?
No response
Describe the feature
Mason.nvim is a plugin manager for NeoVim that contains a library of LSP compatible formatters and linters.
It draws from the registry here: https://github.com/mason-org/mason-registry/tree/main
Being able to pull this data and automatically add support for language formatters / linters from this library of formatters and linters would massively expand the number of languages that are supported by rules_lint.
I've not looked into the feasibility of this but I suspect that we could modify rules_lint to provide a wrapper that supports the LSP protocol that is used by VSCode / NeoVim etc.. and provide a generic linting / formatting capability via this.
Beta Was this translation helpful? Give feedback.
All reactions