chore: add en strings for unknown command #2262
Merged
Conversation
This file contains 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
bcoe
approved these changes
Nov 21, 2022
|
@shadowspawn thank you 👏 , I will need to fix up the npm installation before we can merge (looks like 9.x doesn't like Node 12). Perhaps over holidays this year I'll drop Node 12, and simplify yargs' build. |
|
@shadowspawn thanks for the contribution \o/ |
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.
Adds the unknown command strings to the
enlocale. This has no affect on the output, since they are the same as in the code! The intent is so people updating or creating other locales can see the strings available for localising.Placing the strings after unknown argument in the same place as in the
frlocale from #1560, which looks a good place.Closes: #2259