cloudfoundry / cloudfoundry/cli
Please make maxChoices not a fixed number
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 1.9k
- Forks
- 990
- Avg merge
- 1d 7h
- Merged PRs (30d)
- 8
Description
Please provide details on the following items. Failure to do so may result in deletion of your feature request.
What's the user value of this feature request?
Users can see more than 50 orgs after logging in.
Who is the functionality for?
Everyone having more than 50 orgs.
How often will this functionality be used by the user?
Every day.
Who else is affected by the change?
should not affect the majority of users.
Is your feature request related to a problem? Please describe.
Entering the exact org name is very tedious after having more than 50 entries, because you cant see them anymore.
Describe the solution you'd like
It should be possible to set maxChoices as a variable to increase it to e.g. 100 as a user.
Describe alternatives you've considered
Alternatively, if you want to hardcode it, just increase the maxChoices.
Additional context
Its currently hardcoded to 50. See here:
https://github.com/cloudfoundry/cli/blob/8ca11b656297aca2da6376da2345f0e190d27924/cf/commands/login.go#L24
Note:
As of the GA of the v7 CLI, the v6 line is no longer under active development and will be updated only to patch CVEs or fix severe blocking defects with no workarounds.
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 reading cf/commands/login.go at the referenced maxChoices definition and trace how the organization choices are displayed during login. Check whether the v6 CLI has an existing configuration path for this value. Done means users can see more than 50 organizations without entering the exact name, with the existing login behavior preserved for other users.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100