Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Linters not in mapping cannot be resolved #14

Open
laurentgoudet opened this issue Jul 17, 2024 · 1 comment
Open

Linters not in mapping cannot be resolved #14

laurentgoudet opened this issue Jul 17, 2024 · 1 comment

Comments

@laurentgoudet
Copy link

I am using psalm as a linter (as the language server is cooked for my project) but it seems that mason-nvim-lint cannot auto-install it, i.e. getting Linter [psalm] cannot be resolved into a Mason package. Make sure to only provide valid linter names.

Adding the linter to mapping.lua solves the issue, but as the linters list at https://github.com/mfussenegger/nvim-lint?tab=readme-ov-file#available-linters is far longer than the one in https://github.com/rshkarin/mason-nvim-lint/blob/main/lua/mason-nvim-lint/mapping.lua, I wonder how that plugin is meant to work: do all the packages need to be mapped (even if the tool name & nvim-lint names are the same)? If that's the case, should there be a default mapping (when the names are consistent)?

@laurentgoudet
Copy link
Author

Created a PR to add psalm but let me know if that not the best solution/if a fallback should be more suitable.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant