Conversation
Contributor
283c394 to
6df3806
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
We have performed a comprehensive restructuring of your JSON translation keys, moving from a command-centric, flatter structure to a logical, hierarchical, and standardized taxonomy.
1. Shift to a Standardized Taxonomy
The core change is organizing the data around four main semantic blocks:
common: General utility terms (yes,no,none).program: CLI-level information (version, help, global program description).commands: The central block containing all keys specific to command descriptions, arguments, and options (e.g.,new,config,template,list,info).messages,errors,warnings: Dedicated blocks for unifying all user feedback and execution outcomes (success, failure, status updates).2. Rationalizing Command Structure
All keys related to specific commands were centralized under the new
commandsroot.Example:
Keys previously scattered or prefixed with
cli.(likecli.add_template.description) are now logically grouped by command and subcommand:add,remove) are grouped undercommands.template.newproject command are undercommands.new.This creates a clear, predictable path for every command option and argument.
3. Unification of Output Messages
This is the most critical change for future maintenance. All messages displayed to the user (excluding command descriptions) are now separated into dedicated blocks, allowing for consistent management of tone and outcome:
messagesmessages.status.config_loading), success confirmations (messages.success.config_updated), and scaffolding steps.errorserrors.generic), validation issues (errors.validation), and command-specific problems (errors.command).warningsBy separating UI definitions (under
commands) from execution feedback (undermessages,errors,warnings), the JSON file is now significantly easier to navigate, translate, and maintain.Fixes # (issue)
Type of change
Checklist: