-
Notifications
You must be signed in to change notification settings - Fork 214
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
Fix loading skeletons #3414
Fix loading skeletons #3414
Conversation
Signed-off-by: Olga Bulat <obulat@gmail.com>
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.
Good find, nice fix, thanks!
Size Change: +20 B (0%) Total Size: 1.01 MB ℹ️ View Unchanged
|
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.
You can use throttling in the browser developer tools if your network is too fast to see the loading skeletons.
Wow I had no idea this existed, so cool!!
The skeleton does show up for me when I try to run a search 🦴
Fixes
Follow up on #3341
Description
The linked PR removed the deprecated usage of
this
in a prop validator. However, the template wasn't updated, so the grid skeleton does not show up anymore. This PR fixes it, replacingnumElemss
withelementCount
in the template.Testing Instructions
Run the Nuxt app and search for something. You should see the loading skeletons before the results load. You can use throttling in the browser developer tools if your network is too fast to see the loading skeletons.
Checklist
Update index.md
).main
) or a parent feature branch.Developer Certificate of Origin
Developer Certificate of Origin