Cache per-asset constraint map in graph view#76
Merged
VPDPersonal merged 1 commit intoJun 23, 2026
Merged
Conversation
be5b185
into
feature/serialize-reference-dropdown
1 check passed
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
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.
Summary
SerializeReferenceGraphViewso opening the "Fix Missing" / "Change" picker no longer re-runsBuildConstraintMap(aLoadAllAssetsAtPath+ fullSerializedObjectwalk) on every card click.SerializeReferenceProjectViewpattern: an instance_constraintCachekeyed by asset path, populated lazily inResolveConstraint(now an instance method) and cleared at the top ofRescan(which every apply path funnels through) so a fix's rewritten YAML is re-read.Notes for review
_constraintCache.Clear()lives at the start ofRescan;ApplyFix,ClearReference,ApplyLive, andClearOrphanall end by callingRescan, so the cache can never serve a map staled by an in-view edit.Linked issues
Refs #49 - addresses review finding #49 (comment)