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
Currently we can declare reducers in module hierarchy. We still always provide the root Store though. It would be nice if we could further separate individual modules, allowing them to request only the innermost FeatureStore (which is a view of the store for a specific feature).
(ngrx is great BTW)
The text was updated successfully, but these errors were encountered:
(we refer to MyAppState and ROOT_STORE in child module for type safety, but could skip this and use string as a type token if we want complete separation)
Your solution is how we would recommend going about this. We thought long and hard about whether or not we should scope instances of Store to feature state and ultimately came to the conclusion that - while powerful - it can be very confusing to track what instances of Store are received by which components. It also complicates deriving state from multiple features, a pattern that is common in our own applications.
Currently we can declare reducers in module hierarchy. We still always provide the root Store though. It would be nice if we could further separate individual modules, allowing them to request only the innermost FeatureStore (which is a view of the store for a specific feature).
(ngrx is great BTW)
The text was updated successfully, but these errors were encountered: