You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Mar 1, 2024. It is now read-only.
when a Product query is invalidated all the sub-queries that are part of it get invalidated too (ex const prod = product({ user, preferences }).invalidate() invalidates prod but also user and preferences). This makes it easy to mistakenly invalidate bigger chunks of data than actually needed and hides important details when invalidating (you only explicitly mention prod in the invalidation).
The same arguments applies to Composition as const comp = compose( user, preferences).invalidate() invalidates comp and also user and preferences.
The proposal is to leave invalidate only on CachedQuery and progressively mark it "deprecated" and then remove it from Product and Composition
The text was updated successfully, but these errors were encountered:
fes300
added
the
proposal
issues describing early stage proposals that needs to be further discussed before implementation
label
Jul 1, 2019
when a
Product
query is invalidated all the sub-queries that are part of it get invalidated too (exconst prod = product({ user, preferences }).invalidate()
invalidatesprod
but alsouser
andpreferences
). This makes it easy to mistakenly invalidate bigger chunks of data than actually needed and hides important details when invalidating (you only explicitly mentionprod
in the invalidation).The same arguments applies to
Composition
asconst comp = compose( user, preferences).invalidate()
invalidatescomp
and alsouser
andpreferences
.The proposal is to leave
invalidate
only onCachedQuery
and progressively mark it "deprecated" and then remove it fromProduct
andComposition
The text was updated successfully, but these errors were encountered: