Improve dashboard & coaching session page data fetching and caching #56
Conversation
This file contains 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
… around so the dashboard page can be server side while the SelectCoachingSession component is client side (still)
…oachingRelationship and CoachingSession. Introduces use of SWR for fetching these entities in a very component-friendly manner. Reworks all of the Dashboards 3 selectors into separate components.
…emains compatible for components that aren't yet fully supporting React @19
…turbopack is for dev build
incodable
approved these changes
Dec 23, 2024
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.
Description
This PR makes a significant jump in terms of the maturity of the pattern of fetching and caching backend entity data on the frontend client side.
It now uses SWR for most entity fetching (still using Axios for the actual fetch).
It also updates to use React@19 and Next@15.
Note: it's a bit of a large PR, but it's really not that complex. The same pattern is repeated for each major entity type.
GitHub Issue: none
Changes
AppStateStorewithOrganizationStateStore,CoachingRelationshipStateStore,CoachingSessionStateStoreuseEffectusesScreenshots / Videos Showing UI Changes (if applicable)
N/A
Testing Strategy
mainbranchConcerns
None