fix(hooks): revalidate orphan deliverable on any planning event#2646
Open
gularsson wants to merge 1 commit into
Open
fix(hooks): revalidate orphan deliverable on any planning event#2646gularsson wants to merge 1 commit into
gularsson wants to merge 1 commit into
Conversation
useDeliverableInfo filtered planning events by the stored planningUuidRef. When the initial fetch returned no planning (orphan timeless row, race during creation), the ref stayed undefined and the filter never matched, so the row never recovered without a full reload. Track first-resolve separately; when resolved with no planningUuid, revalidate defensively on any planning event. After adoption the strict match path takes over again. Existing "skip events while pending" behavior is preserved. Refs ELELOG-689 (I7).
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
1 participant
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.
useDeliverableInfo filtered planning events by the stored planningUuidRef. When the initial fetch returned no planning (orphan timeless row, race during creation), the ref stayed undefined and the filter never matched, so the row never recovered without a full reload.
Track first-resolve separately; when resolved with no planningUuid, revalidate defensively on any planning event. After adoption the strict match path takes over again. Existing "skip events while pending" behavior is preserved.
Refs ELELOG-689 (I7).