-
Notifications
You must be signed in to change notification settings - Fork 2k
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
Add loading state for the all domain list item component #43864
Add loading state for the all domain list item component #43864
Conversation
Here is how your PR affects size of JS and CSS bundles shipped to the user's browser: Sections (~458 bytes added 📈 [gzipped])
Sections contain code specific for a given set of routes. Is downloaded and parsed only when a particular route is navigated to. Async-loaded Components (~9 bytes added 📈 [gzipped])
React components that are loaded lazily, when a certain part of UI is displayed for the first time. Legend What is parsed and gzip size?Parsed Size: Uncompressed size of the JS and CSS files. This much code needs to be parsed and stored in memory. Generated by performance advisor bot at iscalypsofastyet.com. |
Actually my idea was to also create the actual domain item component render method that should show fading placeholders while the data is loading |
43501a2
to
0534bcb
Compare
Changes look good to me, and work fine. Could you please add testing instructions next time? It took me some time to understand what pieces were changed, and how to access them. I've also found that adding a screenshot to help a lot for reviews. |
My bad. The task evolved after the initial review. I should have added the new instructions. |
0534bcb
to
14a0a6b
Compare
Changes proposed in this Pull Request
isLoadingDomainDetails
to denote the loading status forDomainItem
components.isLoadingDomainDetails
is true.