microsoft / microsoft/vscode-generator-code

Scaffold localization in an extension

Open
#381 0 comments 1 reaction 1 assignee View on GitHub

@TylerLeonhardt is already working on this.

Since Oct 24, 2022.

feature-request
Dominant language
JavaScript
Stars
1.6k
Forks
262
Avg merge
15d 22h
Merged PRs (30d)
1

Description

I wonder if we can update https://github.com/microsoft/vscode-generator-code to scaffold the l10n directory, add the required "l10n" key to the package.json (once the proposed API is finalized of course), and even include a sample script like the cli.ts. Then we could also have a step in the extension generator which asks you "Do you want to set up localization for this extension" or similar.

Yeah I like this a lot. I'm thinking such a script could:

  • create an l10n folder
  • update the l10n in package.json
  • add @vscode/l10n-dev as a dev dependency
  • create a package.nls.json with {} and a big useful comment

I think that @vscode/l10n's scenario is so uncommon that it's probably not worth including that in the generator IMO. Like it's only gonna be useful if your extension has like... a language server or debug adapter written in node (in other words... subprocesses that will only be used by VS Code that aren't in the extension host)

Originally posted by @TylerLeonhardt in https://github.com/microsoft/vscode/issues/162023#issuecomment-1263830524

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.