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

lsp_store: Do not associate a language server with the language for symbol highlighting #23401

Merged
merged 1 commit into from
Jan 21, 2025

Conversation

osiewicz
Copy link
Contributor

@osiewicz osiewicz commented Jan 21, 2025

This unblocks work on #22182; a single language server might actually be required by multiple languages (think of e.g. C/C++, Javascript/Typescript), in which case it doesn't make sense to use a single grammar. We already use primary language of a buffer for highlights and this PR makes this the only supported syntax highlighting flavour for returned symbols.

Closes #ISSUE

Release Notes:

  • N/A

…ymbol fallbacks

This unblocks work on #22182; a single language server might actually be required by multiple languages (think of e.g. C/C++), in which case it doesn't make sense to use a single grammar. We already use primary language of a buffer for highlights and this PR makes this the only supported syntax highlighting flavour for returned symbols.
@cla-bot cla-bot bot added the cla-signed The user has signed the Contributor License Agreement label Jan 21, 2025
@osiewicz osiewicz merged commit f33d02c into main Jan 21, 2025
13 checks passed
@osiewicz osiewicz deleted the lsp-store-no-language-fallback branch January 21, 2025 12:35
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
cla-signed The user has signed the Contributor License Agreement
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant