How to keep ngrx store only in Module federated standalone UIs and not part of shell UI #4052
Unanswered
kuldeepGDI
asked this question in
Q&A
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
We have a use case where we are combining different module federated components on a single shell UI. The MFcs are part of standalone UIs that have their own larger business logic context. However, the components that are module federated share some states and therefore the ngrx store is used in one of the standalone UIs.
Now when we move to shell UI none of the other standalone UIs except one uses ngrx store currently. Therefore, it does not feel nice to have ngrx store forRoot initilaization in the shell UI and ngrx specific configs shared via webpack config between shell and standalone UIs (I assume we have to then also share ngrx on those standalone UIs that do not use ngrx store at all for now, but i have not tested this).
My question is if there is an alternative way to not enforce ngrx dependency on the shell UI as shell UI simply displays the module federated components from different standalone UIs and has no interdependencies. The suggestion given here works but I am looking for some alternative solutions to not have this hard dependency on ngrx store in the shell UI.
Also similar discussion here #3700 (comment)
Thanks
Beta Was this translation helpful? Give feedback.
All reactions