Replies: 1 comment
-
Hello! This depends on what tools you use to integrate the tools inside Neovim, and is unrelated to mason.nvim (which only installs these). |
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
-
This case might be rare, or maybe you use YAMLs in different contexts too.
So I have the following installed:
Now note that I have 2 workspaces:
cfn-lint
)As you can guess, what I need is that when using the CloudFormation workspace, the cfn linter should be active over the default yaml linter. This is because the yaml linter can't understand the cfn related keywords and functions.
All the other features of the yaml LSP should still be available.
And in the OpenAPI spec workspace, the yaml LSP should work as normal. Or maybe I can find an OpenAPI specific linter and that can take priority.
Is this possible?
P.S Also could there be any reason why yaml formatters like
yamlfmt
andyamlfix
don't work and return[LSP] Format Request failed, no matching language servers
even when:LspInfo
shows "1 client(s) attached to this buffer".Beta Was this translation helpful? Give feedback.
All reactions