Skip to content

Fix LSP default language configuration - #407

Merged
usr3-1415 merged 1 commit into
esa:masterfrom
sylvesterkaczmarek:fix/lsp-default-language
Sep 20, 2026
Merged

usr3-1415 merged 1 commit into
esa:masterfrom
sylvesterkaczmarek:fix/lsp-default-language

Conversation

@sylvesterkaczmarek

Copy link
Copy Markdown
Contributor

Fixes #393.

The LSP front-end settings had C as the active language globally but an empty basic-language map, causing textDocument/didOpen to fail in getBasicLang.

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:

  • reproduced the KeyNotFoundException on current master with an LSP initialize/initialized/didOpen sequence
  • repeated the same sequence after the fix and received textDocument/publishDiagnostics with no exception
  • dotnet build lsp/Server/Server/Server.csproj -c Release passes on .NET 10

@usr3-1415
usr3-1415 merged commit 89bb99f into esa:master Sep 20, 2026
@sylvesterkaczmarek

Copy link
Copy Markdown
Contributor Author

Thanks for merging this. Much appreciated.

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 Server crashes on textDocument/didOpen with KeyNotFoundException in getBasicLang

2 participants