fix(store): improve loose mode invalidation for listing models
#294
+52
−24
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.
• Fixed listing model invalidation bug: Listing models with
loose: truestorage now properly invalidate when items are changed or added• Renamed cache API: Changed
cache.set()tocache.sync()for clearer semantics and addedentry.resolved = trueto prevent duplicate getter calls• Simplified validation logic: Store now uses
entry.resolvedandvalidate()checks instead of complex model state comparisons for cache invalidation• Updated tests: All cache tests now use
sync()instead ofset(), plus added new test to verify listing invalidation works correctly in loose mode