Skip to content

lsp: Check diagnostic refresh capabilities against nil values & support more clients #1398

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

Conversation

osiewicz
Copy link
Contributor

Fixes #1396

@jakebailey
Copy link
Member

Is this patching required? You said in the issue that the protocol was fine, so I was expecting a change that just did a nil check.

@osiewicz
Copy link
Contributor Author

No, it's not. I opened this PR before I wrote the comment in question. I'll fix up this PR in a bit.

@osiewicz osiewicz force-pushed the 1396-check-diagnostic-support-in-caps-against-nil branch from 9327e71 to e5e1a27 Compare July 12, 2025 15:42
@jakebailey jakebailey added this pull request to the merge queue Jul 12, 2025
Merged via the queue into microsoft:main with commit 2b82831 Jul 12, 2025
22 checks passed
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.

lsp(zed): UpdateDiagnostics can end up panicking due to null pointer dereference
2 participants