feat(client): Add a loading skeleton for the Dashboard page - #185
Open
Daksh7785 wants to merge 1 commit into
Open
feat(client): Add a loading skeleton for the Dashboard page#185Daksh7785 wants to merge 1 commit into
Daksh7785 wants to merge 1 commit into
Conversation
👷 Deploy request for intellicircle pending review.Visit the deploys page to approve it
|
|
Someone is attempting to deploy a commit to the Dharm3112's projects Team on Vercel. A member of the Team first needs to authorize it. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What does this PR do?
This Pull Request introduces a responsive loading skeleton for the Dashboard page (
packages/client/src/app/(app)/dashboard/loading.tsx). It utilizes Next.js App Router's nativeloading.tsxfeature to show a beautiful,animate-pulsefallback while the page's client components are hydrating or fetching data.Why is this necessary?
As per Issue #3, users experienced a jarring blank screen or a very rudimentary loading state before the dashboard fully loaded. This new skeleton precisely mirrors the grid layout, action cards, and the mini profile section to provide a seamless and professional user experience, minimizing perceived loading times.
How was this verified?
npm run checkinsidepackages/client).animate-pulseeffect with Tailwind CSS.dashboard/page.tsxincluding the Lucide icons placement.Thank you for reviewing my PR! Let me know if any changes are required, I am happy to accept constructive feedback as per our community Code of Conduct.