Broken L10n using key as fallback
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 24.1k
- Forks
- 2k
- Avg merge
- 1d 5h
- Merged PRs (30d)
- 365
Description
Nushell v0.108.0 just released which included a bump of all uutils to v0.2. This broke verbose flags as it can't load the localization files for some reason and instead falls back to just printing the key (instead of falling back to en-US?)
Running this:
touch foo
mv -v foo bar
Prints this:
mv-verbose-renamed
Instead of the expected message indicating a file has been renamed and printing the old & new paths.
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
Reproduce the issue with touch foo followed by mv -v foo bar on Nushell v0.108.0, then trace how the mv-verbose-renamed localization key is loaded and how missing translations fall back after the uutils v0.2 bump. Done means the command prints a message indicating the rename and includes both the old and new paths.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- cli, localization
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100