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

Add capability information to the metamodel #1591

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

MariaSolOs
Copy link
Contributor

@MariaSolOs MariaSolOs commented Nov 30, 2024

@@ -25,6 +25,7 @@ export namespace ConfigurationRequest {
export const type = new ProtocolRequestType<ConfigurationParams, LSPAny[], never, void, void>(method);
export type HandlerSignature = RequestHandler<ConfigurationParams, LSPAny[], void>;
export type MiddlewareSignature = (params: ConfigurationParams, token: CancellationToken, next: HandlerSignature) => HandlerResult<LSPAny[], void>;
export const capabilities: { client: 'workspace.configuration'; server: 'workspace' } = { client: 'workspace.configuration', server: 'workspace' };
Copy link
Contributor Author

Choose a reason for hiding this comment

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

@dbaeumer The spec doesn't mention a server capability for the workspace/configuration request so I'm unsure about this. Since this is requested by the server it seems like there's no server capability needed here?

@@ -59,6 +59,7 @@ export namespace CallHierarchyPrepareRequest {
export const messageDirection: MessageDirection = MessageDirection.clientToServer;
export const type = new ProtocolRequestType<CallHierarchyPrepareParams, CallHierarchyItem[] | null, never, void, CallHierarchyRegistrationOptions>(method);
export type HandlerSignature = RequestHandler<CallHierarchyPrepareParams, CallHierarchyItem[] | null, void>;
export const capabilities: { client: 'textDocument.callHierarchy'; server: 'callHierarchyProvider' } = { client: 'textDocument.callHierarchy', server: 'callHierarchyProvider' };
Copy link
Contributor Author

Choose a reason for hiding this comment

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

@dbaeumer Do you think we should add capability information for requests like callHierarchy/incomingCalls that don't define their own capabilities and instead depend on whether the server supports other methods (in this case textDocument/prepareCallHierarchy)?

@MariaSolOs MariaSolOs force-pushed the capabilities branch 3 times, most recently from c10685b to 24151f6 Compare December 1, 2024 03:51
@MariaSolOs MariaSolOs marked this pull request as ready for review December 1, 2024 21:48
@MariaSolOs
Copy link
Contributor Author

@microsoft-github-policy-service agree

@dbaeumer
Copy link
Member

dbaeumer commented Dec 9, 2024

@MariaSolOs just a heads up. We have house keeping month in Dezember. New features have to wait until next year.

@MariaSolOs
Copy link
Contributor Author

@MariaSolOs just a heads up. We have house keeping month in Dezember. New features have to wait until next year.

Thanks for the heads-up. Although this isn't user facing so I wouldn't consider it a new feature per se, I understand. I'll wait until January then!

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.

Include capability property path information in the metamodel
2 participants