PowerShell / PowerShell/vscode-powershell

Use localizable resources for all user-facing strings

Open
#585 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Area-UI Issue-Enhancement
Dominant language
TypeScript
Stars
1.9k
Forks
547
PR merge metrics
No merged PRs in 30d

Description

This issue has no description.

Contributor guide

Open the contributing guide

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.

Research direction

The issue body does not identify files, tests, or an existing resource mechanism. Start by locating user-facing strings in the TypeScript extension and determine how localizable resources are currently handled; done means all such strings use that approach and the extension's relevant tests pass.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
localization
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
15/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.