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
In my opinion ngrx/store performs poor in regards to reusability. Recently I opened an issue in ngrx/store and got the advice to add a scope string field to my action in order to re-use my reducer. That works but has its drawbacks.
I guess a lot of issues can be resolved (especially effect reuse through extending .ofType() and so on with it) trough adding a scope?: string; field to the {Action} from '@ngrx/store';
Also i think ngrx/store should promote one way of doing it. E.g. should an action have a scope that you pass in when you call the action or should there be a single action for each re-used slice of your state?
Also how should effects be re-used? Afaik the @Effect annotation doesn't work in abstract classes yet.
The text was updated successfully, but these errors were encountered:
In my opinion
ngrx/store
performs poor in regards to reusability. Recently I opened an issue in ngrx/store and got the advice to add a scope string field to my action in order to re-use my reducer. That works but has its drawbacks.I guess a lot of issues can be resolved (especially effect reuse through extending
.ofType()
and so on with it) trough adding ascope?: string;
field to the{Action} from '@ngrx/store';
Also i think
ngrx/store
should promote one way of doing it. E.g. should an action have a scope that you pass in when you call the action or should there be a single action for each re-used slice of your state?Also how should effects be re-used? Afaik the
@Effect
annotation doesn't work in abstract classes yet.The text was updated successfully, but these errors were encountered: