Add deprecated property to CompletionItem and SymbolInformation #465
Conversation
This file contains hidden or 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
It should be possible for completion items and symbols to be flagged as being deprecated. Some editors and IDEs flag such deprecated items by applying a visual affordance such as striking the text out. By introducing this new deprecated property, these editors and IDEs will be able to use its deprecation UI affordance when supporting a language via the LSP. Signed-off-by: Remy Suen <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
It should be possible for completion items and symbols to be flagged as being deprecated. Some editors and IDEs flag such deprecated items by applying a visual affordance such as striking the text out. By introducing this new deprecated property, these editors and IDEs will be able to use its deprecation UI affordance when supporting a language via the LSP.
This implements and closes #139.
See microsoft/vscode-languageserver-node#332 for the VS Code implementation.