Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature and Root normalized state #37

Open
cam-m opened this issue Jul 6, 2018 · 0 comments
Open

Feature and Root normalized state #37

cam-m opened this issue Jul 6, 2018 · 0 comments

Comments

@cam-m
Copy link

cam-m commented Jul 6, 2018

Hi,

I've an existing app using your library with the normalized reducer in the root app module. I'm now trying to add normalized state to a feature module, while also keeping the root normalized state.

To enable the normalizing reducer to store normalized data, you have to add it to your state. The best place for this might be the root state of your application, but feature states may use their own normalized state as well.

My feature module's state extends NormalizedState and I've added the normalized reducer to my reducer map.

How do I ensure that the schema bound actions are only picked up in the feature state? At the moment both the root and the feature normalized reducers are handling schema bound actions, resulting in duplicated state in the store.

Thanks!

Cam

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant