Skip to content

Include capability property path information in the metamodel #2059

@MariaSolOs

Description

@MariaSolOs

It would be helpful for the metamodel to include the property path of the respective client/server capabilitiy for each request. E.g.: The client capability for textDocument/declaration request is found in textDocument.declaration (in the client's capabilities object) and similarly support in the server side is found at declarationProvider.

This information is already available in the spec's website, but for consumers of the metamodel having the capability information would be quite helpful.

Metadata

Metadata

Assignees

No one assigned

    Labels

    feature-requestRequest for new features or functionalityhelp wantedIssues identified as good community contribution opportunities

    Type

    No type

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions