If the users selects a language, let's have it actually choose the language they selected. (Yaml vs yaml)

[Infro]

Untested - Use Id instead of fuzzy lookup (Yaml vs yaml)
Too simple for an issue.
Two line change which changes identifying with a string to identifying them with the id. WOW

[vs-code-engineering]

📬 CODENOTIFY

The following users are being notified based on files changed in this PR:

@bpasero

Matched files:

• src/vs/workbench/browser/parts/editor/editorStatus.ts

[Copilot]

Pull request overview

This PR fixes a bug in the language selection feature where selecting a language (e.g., "YAML") from the quick pick would not reliably select the correct language ID due to case-sensitive fuzzy lookup. The fix replaces the indirect lookup via languageName with direct usage of the languageId stored in the quick pick item's id field.

Changes:

• Added id: languageId field to language quick pick items to store the precise language ID
• Changed language selection logic to use pick.id instead of performing a fuzzy name lookup via getLanguageIdByLanguageName(pick.label)

Comments suppressed due to low confidence (1)

src/vs/workbench/browser/parts/editor/editorStatus.ts:1289

• This line still uses the old fuzzy lookup approach via getLanguageIdByLanguageName(pick.label). It should be updated to use pick.id for consistency with the fix on line 1284. This inconsistency could cause the telemetry to report incorrect language IDs when the label doesn't match exactly (e.g., 'YAML' vs 'yaml').

							const chosenLanguageId = languageService.getLanguageIdByLanguageName(pick.label) || 'unknown';

[bpasero]

What bug does this fix?

[Infro]

When multiple languages exist with differently cased names. You can only change to one of them. Eg Yaml vs yaml then no matter which you select, it'll choose Yaml. This lets you select either one .