Repository navigation
FIX: Wait for saved profile before fetching topic reports - #154
Merged
Merged
Conversation
iansargent
self-requested a review
October 9, 2026 14:14
iansargent
approved these changes
Oct 9, 2026
iansargent
left a comment
iansargent
left a comment
Collaborator
There was a problem hiding this comment.
Looks good to me! Hopefully saves some compute and rendering time!
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.
On a full page load of Reports by Topic, the page fetches data twice: once for the default profile (Vermont vs. Vermont), then again for the saved profile. The first set of responses is discarded, so the data shown is correct, but the requests are wasted. This PR adds a useProfileHydrated hook and waits for the saved profile to load before fetching. Other views that read the profile on load can use the same hook.
Note: This PR is intentionally small and non-invasive so that we can have a PR to walk through deployment process.