cloudfoundry / cloudfoundry/cli
Deprecate --locale support
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 1.9k
- Forks
- 990
- Avg merge
- 1d 7h
- Merged PRs (30d)
- 8
Description
Localization in the cf-cli is turned on via cf config --locale (some locale), but due to lack of maintenance of the CLI-side translations, doing so does not have the desired effects. Often, commands will have none, or just a small part of its output translated, leading to an uneven experience.
Unless the process of maintaining the translation is resurrected, we may want to consider deprecating the localization functionality instead of misleading the user, and cleaning it out from the code.
Relevant Slack: https://cloudfoundry.slack.com/archives/C032824SM/p1768979476036379?thread_ts=1768378778.410389&cid=C032824SM
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 tracing the cf config --locale entry point and the CLI-side translation code, then review the linked Slack discussion for the maintenance decision. Done means the agreed deprecation and cleanup scope is implemented without leaving misleading localization behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- cli, internationalization
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100