Skip to content
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

Merged
merged 2 commits into from
Apr 6, 2021

Conversation

evidolob
Copy link
Collaborator

What does this PR do?

Use 'markdownDescription' for property completion.
Demo:
Screenshot 2021-03-25 at 12 05 03

What issues does this PR fix or reference?

Fix: redhat-developer/vscode-yaml#417

Is it tested? How?

With test

@evidolob evidolob self-assigned this Mar 25, 2021
@coveralls
Copy link

coveralls commented Mar 25, 2021

Coverage Status

Coverage increased (+0.1%) to 79.436% when pulling f90ad78 on evidolob:fix-i417 into 17edd7c on redhat-developer:master.

required: ['kind'],
});

const content = 'kin';
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should kin be kind?

Copy link
Collaborator Author

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

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ok

Copy link
Contributor

@JPinkney JPinkney left a 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

@evidolob
Copy link
Collaborator Author

evidolob commented Mar 25, 2021

@JPinkney In all cases we use fromMarkup Which already has such check.
I will double check that we use that method.

@evidolob evidolob merged commit 88813e2 into redhat-developer:master Apr 6, 2021
@evidolob evidolob deleted the fix-i417 branch April 6, 2021 14:00
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

vscode/jsonschema markdownDescription support seems patchy
4 participants