Skeleton loader for staffing #675
Open
Conversation
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
Useful for instance when you don't want to immediately show a skeleton/loader, such as for data which typically loads very fast. This prevents loaders flashing
merging to get react query
merging to get tanstack
robines
approved these changes
Feb 25, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Skeleton loader for staffing done! I am open to feedback on the naming here, the page now does not have any fetching, (only prefetching of consultants, can do customers, departments etc as well but consultants is the biggest one), and then there is a content.tsx but since there is also a StaffingContent.tsx I decided to name export the content.tsx as Staffing. Lmk if anyone has a better idea:))
https://github.com/user-attachments/assets/dc789805-8a41-4b01-9156-fd62b4f71206