-
Notifications
You must be signed in to change notification settings - Fork 88
CLOUDP-114891: Improve org/project selection when too many orgs/projects #1025
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
|
Making some copy suggestions global user not in VPNFor the below case, would it be possible to do sth like this: More than 100 resultsThis way, it could be the same experience for any amount of orgs and projects. |
|
I think the proposed solution as a quick fix works well. My only concern is the number "100". I quickly asked two CLI users how many items in a selection list they think is maximum and they both told me 10, at most 20. If Jakub could get the number of how many projects in an organization for our users, the data could also be helpful. My suggestion is, if in more than 99% cases, there are less than 20 projects in an Org, then we could go with the solution Guss proposed but change "100" to "20". Also some proposed copy changes: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
code review - LGTM
|
@boooczek we can't change the error message here that comes from the API, I can make the change separately from these changes @boooczek @dianchenghu sorry if I missed to explain this but... The results of fetching orgs and projects is paginated with a default page size of 100 and a hard limit of 500 per page, this is where the number 100 came from but feel free to pick any number between 1 and 500 while keeping in mind the following Currently the org/project selects need to be created with all selectable values before hand, it can't: all of the above options require investigation time to implement our own custom select and with no clear idea currently if any of those options are really possible Based on those points is important for you both to understand that whatever number we decide, ie 20, if the user happens to want to pick the 21st value it will never be in the list nor we would be able to load it and why the current implementation totally skips the list if more than the limit we decide |
andreaangiolillo
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
|
With what @gssbzn said, I'm suggesting to load the max list of 500. |
Co-authored-by: Andrea Angiolillo <andrea.angiolillo@mongodb.com>
|
@boooczek I've made the change to have a limit on 500 |
|
LGTM |
|
Thank you! lgtm
…On Wed, Mar 9, 2022 at 2:00 PM Diancheng Hu ***@***.***> wrote:
LGTM
—
Reply to this email directly, view it on GitHub
<#1025 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAPN5WKRSRI7NUFKCODV3ZTU7COHFANCNFSM5QGPG27Q>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Proposed changes
Jira ticket: CLOUDP-114891
Checklist
make fmtand formatted my codeFurther comments
global user not in VPN
More than 100 results
Less than 100 results