This repository has been archived by the owner on Sep 20, 2023. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 55
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
refactor!: use vim.diagnostic for lsp provider
BREAKING CHANGE: The `diagnostics_exist` utility function now takes an integer containing the diagnostic severity instead of a string. For more info, do `:help vim.diagnostic.severity` in Neovim.
- Loading branch information
1 parent
996984a
commit 6be9ca2
Showing
2 changed files
with
17 additions
and
17 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
6be9ca2
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi, @ram02z @lukas-reineke
I'm still investigating but I think this may be a breaking change, sorry for the unfortunate news
On Debian,
NvimAppimage 0.5 & 0.6
Update:
so sorry, I've totally blazed past the "Breaking" in the title, still reading
6be9ca2
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Only the
diagnostics_exist
function takes a different argument now.If you get any other errors, can you post them? I can also take a look.
6be9ca2
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@lukas-reineke
So firstly, my apologies, I didn't investigate my config well enough.
It seems that my config referenced some breaking changes, and attempted to use some old (and now non-existent) vim.lsp api calls.
Will update if I actually find an issue, sorry!
6be9ca2
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
bg color in statusline no longer works for me now, after this commit
6be9ca2
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Open an issue please.