diff options
| author | Lewis Russell <lewis6991@gmail.com> | 2024-04-30 09:57:31 +0100 |
|---|---|---|
| committer | Lewis Russell <me@lewisr.dev> | 2024-04-30 13:39:27 +0100 |
| commit | ee41153a945876ad0c7f0927ffa7b5a5afdaca89 (patch) | |
| tree | 6626b81f72f4b38185d3722f9391b4266d4ca26b /runtime/lua/vim/_meta/api.lua | |
| parent | 0330dd9e69de7567fd2479c0203b778a1d2dce2f (diff) | |
| download | rneovim-ee41153a945876ad0c7f0927ffa7b5a5afdaca89.tar.gz rneovim-ee41153a945876ad0c7f0927ffa7b5a5afdaca89.tar.bz2 rneovim-ee41153a945876ad0c7f0927ffa7b5a5afdaca89.zip | |
feat(diagnostic): revert default behaviour of goto_next/prev()
Follow-up to #28490
Problem:
The new behaviour of goto_next/prev() of navigating to the next highest
severity doesn't work well when diagnostic providers have different
interpretations of severities. E.g. the user may be blocked from
navigating to a useful LSP warning, due to some linter error.
Solution:
The behaviour of next highest severity is now a hidden option
`_highest = true`. We can revisit how to integrate this behaviour
during the 0.11 cycle.
Diffstat (limited to 'runtime/lua/vim/_meta/api.lua')
0 files changed, 0 insertions, 0 deletions