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 messageDetails to Diagnostic #1339

Closed

Conversation

RobbyCBennett
Copy link

@RobbyCBennett
Copy link
Author

This is expected to fail until the types are updated. See microsoft/language-server-protocol#1825 (comment)

@dbaeumer
Copy link
Member

dbaeumer commented Dec 5, 2023

I will close the PR for now. Please ping if you decide to continue working on this.

@dbaeumer dbaeumer closed this Dec 5, 2023
@RobbyCBennett
Copy link
Author

I have already prepared this pull request as far as I am able to. The types are incorrect, and there doesn't appear to be any documentation for what repos the types come from.

This PR is waiting for other PRs first.

Please review the other PRs in microsoft/language-server-protocol#1825 (comment), which I think should mostly fix the types.

@dbaeumer
Copy link
Member

dbaeumer commented Dec 6, 2023

Actually there seems to be a misunderstanding. The language server protocol is the specification. They don't define types. IMO your problem is that VS Code itself doesn't support messageDetails (https://github.com/microsoft/vscode/blob/6d1f607c6db3c6d9c842f77a12375ce9900ed53c/src/vscode-dts/vscode.d.ts#L6719) and this repository is the LSP implementation for VS Code. So to get this working messageDetails need to be implemented in VS Code first (see microsoft/vscode#195727)

For the specification: we only merge something into the specification if there is at least one implementation for a client.

Please ping when the VS Code implementation is ready to be consumed and I will reopen the PR.

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.

2 participants