feat: implement dashboard and search components including real-time d…#141
Merged
Conversation
…ata visualization, advanced filtering, and interactive quiz interfaces
|
@T-kesh Great news! 🎉 Based on an automated assessment of this PR, the linked Wave issue(s) no longer count against your application limits. You can now already apply to more issues while waiting for a review of this PR. Keep up the great work! 🚀 |
Contributor
|
please fix ci |
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
2 participants
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.
This PR addresses significant frontend performance bottlenecks resulting from excessive and uncontrolled component re-renders across the Dashboard, Search, and Quizzes modules. To ensure rendering efficiency, all primary wrapper and list components within these targeted views were encapsulated in React.memo, establishing strict prop-based lifecycle updates. Additionally, dynamically calculated states such as complex filter permutations were locally cached using useMemo, and numerous uninstantiated inline methods—including structural drag handlers and interactive click events—were stabilized into persistent memory references using the useCallback hook. These optimizations collectively guarantee a seamless, judder-free user experience without altering previously established interfaces.
Thank you for the giving me the opportunity to work on this.
closes #115