As I was trying out this plugin, I noticed that code actions kept being shown on lines even when actions weren't available:
I dug into this and it seems like the reason is because vim.lsp.diagnostic.get_line_diagnostics() without any arguments seems to get diagnostics across the entire workspace:
I opened this PR as a fix to this by including just the bufnr in the call in case it was on purpose to try and include diagnostics not just on that line. By just adding the buffer it'll include diagnostics across the whole buffer. If we wanted to tighten this more we could add the line number as well but I wanted to open this up for discussion.
As I was trying out this plugin, I noticed that code actions kept being shown on lines even when actions weren't available:
I dug into this and it seems like the reason is because
vim.lsp.diagnostic.get_line_diagnostics()
without any arguments seems to get diagnostics across the entire workspace:I opened this PR as a fix to this by including just the bufnr in the call in case it was on purpose to try and include diagnostics not just on that line. By just adding the buffer it'll include diagnostics across the whole buffer. If we wanted to tighten this more we could add the line number as well but I wanted to open this up for discussion.