-
Notifications
You must be signed in to change notification settings - Fork 26
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
Missing hint
severity for diagnostics
#840
Comments
basedpyright supports the deprecated and unnecessary diagnostic tags for some rules, just like pyright. i'm not sure what the hint diagnostic looks like but i don't think pyright uses it either. i'll look into adding support for it though |
Interestingly, whereas and they are configured pretty much the same way: https://github.com/neovim/nvim-lspconfig/blob/master/lua/lspconfig/configs/basedpyright.lua |
Ok, should have read the docs thoroughly once more. For anybody's reference, setting The rest of my confusion comes from my lack of understanding of how diagnostic severities and tags from basedpyright are mapped to the four possible severities in neovim. But I can find my work around Thanks for your time, feel free to reopen if there's still anything of interest here :) |
no problem, your issue gave me the idea to simplify these hint diagnostics which will hopefully reduce some of the confusion people have had about them - see #845 to summarize, all diagnostics will support the same [tool.basedpyright]
reportUnreachable = "hint" the |
I'm using
basedpyright
together withneovim
, planning to migrate frompyright
. The only thing keeping me is the missinghint
diagnostic severity.Hint
severity is defined both in the MS specification and e.g. in neovim docs.Is there any reason why it cannot be used in
basedpyright
?The text was updated successfully, but these errors were encountered: