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
If you define a store query within a computation, the reactive queries end up being cleaned up which leads to the query becoming non-reactive.
This is just how S works, but I really would like to cache queries. I might disable caching queries for now and think about this as I want to work with the grain of S while also supporting caching queries.
Maybe queries are defined in a separate S.root and have the same lifecycle as the context which created the store. But that may encourage having multiple stores which I don't think is a good approach by default.
Or... we use cleanup hooks in the read stream to deregister/register the store instance. Needs some dogfooding to find the right approach.
The text was updated successfully, but these errors were encountered:
If you define a store query within a computation, the reactive queries end up being cleaned up which leads to the query becoming non-reactive.
This is just how S works, but I really would like to cache queries. I might disable caching queries for now and think about this as I want to work with the grain of S while also supporting caching queries.
Maybe queries are defined in a separate
S.root
and have the same lifecycle as the context which created the store. But that may encourage having multiple stores which I don't think is a good approach by default.Or... we use cleanup hooks in the read stream to deregister/register the store instance. Needs some dogfooding to find the right approach.
The text was updated successfully, but these errors were encountered: