Repository navigation
Preserve query membership while a tag or component relation remains - #61
Merged
HexDecimal merged 1 commit intoOct 15, 2026
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #61 +/- ##
=======================================
Coverage 99.16% 99.17%
=======================================
Files 9 9
Lines 959 965 +6
=======================================
+ Hits 951 957 +6
Misses 8 8 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
HexDecimal
approved these changes
Oct 15, 2026
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.
Removing a tag relation deletes the shared query indexes even when a component relation with the same origin, key and target still exists. Removing the component while keeping the tag has the same problem. Saving and loading rebuilds those indexes, so it unexpectedly changes query results.
Before:
True False True, with component value42still present. After:True True True, with the same component value.Retain the index entry while either backing relation still owns it. Once the final relation is removed, normal index cleanup and cache invalidation continue. The guard checks membership, so a zero-valued component also keeps its relationship.
Regression coverage checks both removal orders, named and type keys, all four relation query forms and final cleanup. Faction-transition workflows with inherited actors and save/load checkpoints match separate dictionary state after the fix. The full suite, strict mypy and project hooks pass; the existing two XPASS cases and pytest parameter-iterator warning remain unchanged. No query syntax, save format or performance claim changes.