fix(frontend): notify subscribers after persisted cache hydration - #413
Open
Alae-Tamouh wants to merge 1 commit into
Open
fix(frontend): notify subscribers after persisted cache hydration#413Alae-Tamouh wants to merge 1 commit into
Alae-Tamouh wants to merge 1 commit into
Conversation
Alae-Tamouh
requested review from
JWThewes,
eipasteur,
jeromevdl,
leandrodamascena and
svozza
as code owners
August 19, 2026 15:35
jeromevdl
reviewed
Aug 20, 2026
jeromevdl
requested changes
Aug 20, 2026
jeromevdl
left a comment
jeromevdl
left a comment
Contributor
There was a problem hiding this comment.
Thanks @Alae-Tamouh for this fix. One minor test improvement before approving.
Alae-Tamouh
force-pushed
the
contrib/persisted-cache-hydration
branch
from
August 24, 2026 07:54
e49a0f7 to
414c593
Compare
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.
Issue #, if available: None
Description of changes:
Problem
Projects and sprints are hydrated from sessionStorage inside mount effects. Subscribers render before hydration and initially observe an empty external store. When the persisted entry is fresh, network revalidation returns early, so no version change occurs and mounted views can remain empty indefinitely.
Solution
Notify the existing project and per-project sprint external-store subscribers immediately after adopting persisted cache entries.
Impact
Dashboard, space, and sprint views rerender with fresh persisted data without requiring an unnecessary network request. Cache TTL and refresh behavior are unchanged.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.