Closed willdavidow closed 1 year ago
Hi! Thanks for catching this bug. I don't have much time lately, but I appreciate the workaround in the meantime.
I also encountered this issue, although ignoring null-ls
in update_lightbulb
didn't work for me. (Since I rarely use the blame line stuff, I have disabled this part of null ls though.)
I copied the config example from the main readme and made adjustments to include
null-ls
in the ignore pattern and have the plugin manage creating autocmds. The issue there is that I see the lightbulb on every single line and it's includingnull-ls
even though I have it in my ignore config.I did some additional testing by setting
autocmd
to false in the config, then added my ownautocmd
with theignore
setting included in every update call, and it works as expected.Long story short: it appears that the
ignore
setting just doesn't work at all when passed into the main plugin configuration and the only way to ignore specific LSP code actions is to include the ignore configuration there.My
nvim-lightbulb
config: