summaryrefslogtreecommitdiffstatshomepage
path: root/runtime/lua/vim/provider/python.lua
diff options
context:
space:
mode:
authorSergei Slipchenko <faergeek@gmail.com>2026-03-21 17:38:11 +0400
committerGitHub <noreply@github.com>2026-03-21 09:38:11 -0400
commit7a5e9ef0aab84bbd69594ceec231db1fb11171f9 (patch)
tree6f5f8cf5df320e8909c99eb1b4d95884a93b3d79 /runtime/lua/vim/provider/python.lua
parent3dbba90ba7644aa7a47bd511823bf66a4f57b22c (diff)
fix(lsp/diagnostic): use diagnostic provider identifier for code actions #38401
Problem: f9b2189b287a14478546da72b7ecdfd3afe981c7 started using namespaces for pull diagnostics that look like this `<id>:<identifier>`. `vim.lsp.buf.codeaction` passes `true` instead of an identifier to `vim.lsp.diagnostic.get_namespace`, resulting in a namespace that looks like `<id>:nil`. The end result is that none of the diagnostics are passed to `textDocument/codeAction` request. Because of that server might not send any code actions back. For example, eslint lsp responds with an empty list of actions if it receives no diagnostics. Solution: use `_provider_foreach` to collect diagnostics from all `identifiers` and use that identifier to get a namespace instead of `true`.
Diffstat (limited to 'runtime/lua/vim/provider/python.lua')
0 files changed, 0 insertions, 0 deletions