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

vscode: add support for the l10n namespace #11893

Closed
Tracked by #12019
msujew opened this issue Nov 21, 2022 · 0 comments · Fixed by #12192
Closed
Tracked by #12019

vscode: add support for the l10n namespace #11893

msujew opened this issue Nov 21, 2022 · 0 comments · Fixed by #12192
Assignees
Labels
localization issues related to localization/internalization/nls vscode issues related to VSCode compatibility

Comments

@msujew
Copy link
Member

msujew commented Nov 21, 2022

With vscode 1.73.0, a vscode native way has been introduced to localize extensions (which was previously done through the vscode-nls package). See their vscode.d.ts file. Microsoft now uses the API starting from 1.73.0 for all their built-in extensions, so we need to support/stub this in case someone wants to use current versions of built-in extensions.

@msujew msujew added vscode issues related to VSCode compatibility localization issues related to localization/internalization/nls labels Nov 21, 2022
@msujew msujew self-assigned this Feb 17, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
localization issues related to localization/internalization/nls vscode issues related to VSCode compatibility
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant