-
-
Notifications
You must be signed in to change notification settings - Fork 4.7k
fix(app-settings): limit app to group initial state #57533
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
base: master
Are you sure you want to change the base?
Conversation
002dc8a to
7bd91a3
Compare
48486dc to
daf55db
Compare
Signed-off-by: Elizabeth Danzberger <[email protected]>
Signed-off-by: Elizabeth Danzberger <[email protected]>
daf55db to
90deae4
Compare
Signed-off-by: Elizabeth Danzberger <[email protected]>
|
Should be ready for a proper review now. Added a Cypress test for coverage. |
|
/backport to stable31 |
|
/backport to stable33 |
|
/backport to stable32 |
susnux
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.
no frontend code needed?
No. The front end already expects the initial state to be there, so we just need to provide it in the backend. Because it wasn't before, it was defaulting to an empty dropdown and only populated it once you started searching. |
Summary
When you try to limit an app by a group, the dropdown is initially not filled with any groups. They only populate once you start typing the name of a group, which triggers a network request. This pull request provides the necessary initial state to the app list so that the groups are populated by default and you can quickly select one without searching.
TODO
Checklist
3. to review, feature component)stable32)