-
Notifications
You must be signed in to change notification settings - Fork 264
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
Use 'markdownDescription' for property completion #431
Conversation
Signed-off-by: Yevhen Vydolob <[email protected]>
required: ['kind'], | ||
}); | ||
|
||
const content = 'kin'; |
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.
Should kin
be kind
?
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.
It should be kin
to test completion to kind
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.
ok
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.
I think we might have to add a CompletionClientCapabilities
check for the documentationFormat. If I'm understanding the spec correctly, under https://microsoft.github.io/language-server-protocol/specification#textDocument_completion it looks like clients can specify what documentation formats they support in completionItem.documentationFormat
@JPinkney In all cases we use fromMarkup Which already has such check. |
…rver into fix-i417 Signed-off-by: Yevhen Vydolob <[email protected]>
What does this PR do?
Use 'markdownDescription' for property completion.
Demo:
What issues does this PR fix or reference?
Fix: redhat-developer/vscode-yaml#417
Is it tested? How?
With test