-
Notifications
You must be signed in to change notification settings - Fork 46
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
[Question] Unable to Ignore Repetitive Suggestions #96
Comments
Looks like this might be the same as #91 -- does that look like the same issue to you? |
Yes, this is the same as #91. Also, the way you would want to use the require('lspconfig').ruff_lsp.setup {
on_attach = on_attach,
init_options = {
settings = {
args = {
"--ignore=E501",
}
}
}
} |
@dhruvmanila But these two suggestions don't have a code to ignore them |
Yes, I think you're confusing code actions with rule codes. If you really want to filter these out unconditionally, you can use the |
I've just stumbled on the same issue. Although I can filter out those two messages with require("lspconfig").ruff_lsp.setup({
init_options = {
settings = {
fixAll = false,
organizeImports = false,
},
},
}) But that also means I cannot use those two actions anymore. I'd love to have those actions implemented as an editor command (like in vscode). Hopefully this will be implemented in the future. |
yes. it works fine for me thank you very match. |
For Neovim you can define these commands similar to VSCode. Please refer to #295 (comment). You can then use a keybinding to execute that command. Hope this helps! |
I am unable to ignore repetitive suggestions in my editor
neovim
while using theLighthub
💡 icon. I have noticed that two suggestions from Ruff keep appearing even though I have already considered them in the past. I believe this is due to my consistent usage of the 💡 which remains visible at all times, leading to the repetition of the same suggestions. Could you please provide a solution to this issue so that I can use my editor without any hindrances?The text was updated successfully, but these errors were encountered: