PowerShell / PowerShell/platyPS
V2 move schema template strings to RESX to allow for localization
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 871
- Forks
- 166
- Avg merge
- 21h 17m
- Merged PRs (30d)
- 1
Description
To support localization, the following strings in the schema for the template need to be localized.
- All schema-defined headers that have labels:
- Cmdlet schema
- Synopsis
- Syntax
- Description
- Examples
- Example
- Parameters
- Common Parameters
- Inputs
- Input type
- Outputs
- Output type
- Notes
- Related links
- About schema
- Short description
- Long description
- See also
- Cmdlet schema
- The text of the CommonParameters paragraph
NOTE: The
H1 Titlefor both cmdlet and about_ files, and theH3 -ParameterNameheadings do not contain values defined by the schema. Therefore, they don't have strings that need to be localized in the PlatyPS module. Also, no strings within a YAML block should be localized. This includes frontmatter and parameter metadata.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the schema template code and its RESX resources in the PlatyPS repository. Identify the listed schema-defined labels and CommonParameters paragraph, then verify that localized resources cover them while H1 titles, parameter headings, YAML blocks, frontmatter, and parameter metadata remain unchanged.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp, powershell
- Domain
- documentation, localization
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100