-
Notifications
You must be signed in to change notification settings - Fork 87
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support all new 3.17 features (except for notebooks) #255
Support all new 3.17 features (except for notebooks) #255
Conversation
d602cd1
to
9843711
Compare
@Marwes Just wanted to send a gentle ping requesting a review. Sorry to do this directly; I only wanted to let you know that there are several downstream projects currently awaiting LSP 3.17.0 support to land. Any feedback would be appreciated. Thanks! ❤️ |
I sometimes point my project to a temporary fork of lsp-types, cargo makes it easy to use git dependencies. |
@krobelus I do too, but only on personal projects or in binary-only crates. I'd hardly like to do that in I could put a big disclaimer on such a release, requesting developers of binary crates depending on |
Added
textDocument/inlineValue
.workspace/symbols
and supportworkspaceSymbol/resolve
.MarkdownClientCapabilities
.UTF8-offsets
extension now?)FileSystemWatcher
sCodeActionKind::SOURCE_FIX_ALL
.Changed
LSPAny
,LSPObject
, andLSPArray
type aliases.textDocument/inlayHint
.proposed
.CompletionItem
s.Fixed
CompletionList
client capability.README.md
.There was a lot of work done here to bring
lsp-types
to actually support the 3.17.0 specification (see official changelog). I chose to not add in notebook support myself, since there seems to be a draft PR already open which tackles that (#229). This work should take care of everything else, though.Closes #238.
Closes #251.
Closes #252.
Blocks ebkalderon/tower-lsp#352.