Fix LSP default language configuration - #407
Merged
usr3-1415 merged 1 commit intoSep 20, 2026
Merged
Conversation
Contributor
Author
|
Thanks for merging this. Much appreciated. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fixes #393.
The LSP front-end settings had C as the active language globally but an empty basic-language map, causing
textDocument/didOpento fail ingetBasicLang.Provide the C basic-language settings used by the front end and make C the explicit default target language. This keeps the LSP independent of the code-generation backend while restoring the expected default configuration.
Validation:
KeyNotFoundExceptionon currentmasterwith an LSP initialize/initialized/didOpen sequencetextDocument/publishDiagnosticswith no exceptiondotnet build lsp/Server/Server/Server.csproj -c Releasepasses on .NET 10