-
Notifications
You must be signed in to change notification settings - Fork 13.9k
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
feat: Update query states to use spinner vs. progress bar #17804
Conversation
Codecov Report
@@ Coverage Diff @@
## master #17804 +/- ##
==========================================
+ Coverage 67.07% 67.11% +0.03%
==========================================
Files 1609 1609
Lines 64899 65016 +117
Branches 6866 6910 +44
==========================================
+ Hits 43533 43636 +103
- Misses 19500 19509 +9
- Partials 1866 1871 +5
Flags with carried forward coverage won't be shown. Click here to find out more.
Continue to review full report at Codecov.
|
/testenv up |
@hughhhh Ephemeral environment spinning up at http://35.164.237.142:8080. Credentials are |
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.
Thanks for fixing!
Ephemeral environment shutdown and build artifacts deleted. |
* lit * remove reference for progress bar * update to loading * update switch out spinner for loading when progress hits 100 * update test
* lit * remove reference for progress bar * update to loading * update switch out spinner for loading when progress hits 100 * update test
SUMMARY
Updated the progress bar to use the spinner in fetching state when progress is 100. Whenever the users lands in a fetching with a large amount of data it causes a bad user experience since it takes a while for the data to render. With the spinner we provide a better experience and provides UI consistency in our loading states.
BEFORE/AFTER SCREENSHOTS OR ANIMATED GIF
TESTING INSTRUCTIONS
ADDITIONAL INFORMATION