-
Notifications
You must be signed in to change notification settings - Fork 3.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
ui: consistent & useful loading indicators [460] #24011
Comments
The second point is covered in #24069. I'm surprised to see that there's not already an issue describing the inconsistent/annoying loading states across all pages. The closest I can find is #19347, though that is restricted to the databases page (which has it's own issues with data loading). So I'm repurposing this issue to stand in for regularizing our loading states across all pages. |
Agree that a consistent pattern for data loading (and error) states deserves its own issue. #1 highest-value refactor we could do to the UI, IMO. |
24855: ui: add data distribution debug page (aka replica matrix) r=vilterp a=vilterp ![image](https://user-images.githubusercontent.com/7341/41315292-0f7d284a-6e5d-11e8-81cb-cacd978cc519.png) Split off from #20500, which had some CR comments from four months ago. Many have been addressed, but need to comb through again. Note: if one of its API calls returns an error, it will display the spinner forever. Sadly, the cluster viz has the same problem (as well as many other pages, probably). Kind of want to address this with some changes to `Loader` as part of #24011, but maybe should just address it here. Co-authored-by: Pete Vilter <[email protected]>
Contributes to: cockroachdb#24011 Release note: None
Contributes to: cockroachdb#24011 Release note: None
Previously, data fetching errors were not being consistently surfaced to the user. This commit updates all existing uses of the Loading component to surface these errors: - Some parent components render data from multiple sources, potentially having multiple errors to show the user. This commit also extends the Loading component to handle multiple errors. - The Certificates page had custom loading logic. This commit replaces logic with Loading component. Also in this commit is some minor cleanup (copy, layout). Fixes: cockroachdb#24011 Release note (admin ui change): This commit wires up data errors to all existing uses of the Loading component. Previously, data errors weren't consistently surfaced.
Previously, data fetching errors were not being consistently surfaced to the user. This commit updates all existing uses of the Loading component to surface these errors: - Some parent components render data from multiple sources, potentially having multiple errors to show the user. This commit also extends the Loading component to handle multiple errors. - The Certificates page had custom loading logic. This commit replaces logic with Loading component. Also in this commit is some minor cleanup (copy, layout). Fixes: cockroachdb#24011 Release note (admin ui change): This commit wires up data errors to all existing uses of the Loading component. Previously, data errors weren't consistently surfaced.
32464: ui: render errors in Loading component r=couchand a=celiala Previously, data fetching errors were not being consistently surfaced to the user. This commit updates all existing uses of the Loading component to surface these errors: - Some parent components renders data from multiple sources, potentially having multiple errors to show the user. This commit also extends the Loading component to handle multiple errors. - The Certificates page had custom loading logic. This commit replaces logic with Loading component. Also in this commit is some minor cleanup (copy, layout). Fixes: #24011 Release note (admin ui change): This commit wires up data errors to all existing uses of the Loading component. Previously, data errors weren't consistently surfaced. Co-authored-by: Pete Vilter <[email protected]> Co-authored-by: Celia La <[email protected]>
no results
when in reality its loadingThe text was updated successfully, but these errors were encountered: