I will go from one menu / item to another directly with the router. And the first step after that will be to activate the feature store. It works well.
As we must be able to install this on-site application with all or only a few features, this architecture will be suitable.
I will study the lazzy loading of the stores.
Your tutorial was a good introduction to solve my problem.
Director of Architecture, Chief Architect at Briebug. Google GDE for Angular/Web Tech. I’m a huge weather nerd. I’m here if you need help in Angular, ASP.Net Core, or best practices.
Location
USA
Education
School of Hard Knocks
Work
Director of Architecture, Chief Architect at Briebug
Lazy loading is easy, we have just to move the featureModules from AppModule in their corresponding module.
In DevRedux we can see a new line with 'update-reducers'
Director of Architecture, Chief Architect at Briebug. Google GDE for Angular/Web Tech. I’m a huge weather nerd. I’m here if you need help in Angular, ASP.Net Core, or best practices.
Location
USA
Education
School of Hard Knocks
Work
Director of Architecture, Chief Architect at Briebug
I will go from one menu / item to another directly with the router. And the first step after that will be to activate the feature store. It works well.
As we must be able to install this on-site application with all or only a few features, this architecture will be suitable.
I will study the lazzy loading of the stores.
Your tutorial was a good introduction to solve my problem.
I plan on updating my article soon to accommodate for lazy loading feature stores, I will also address dispatching actions between feature stores
I will monitor and read the news carefully.
Lazy loading is easy, we have just to move the featureModules from AppModule in their corresponding module.
In DevRedux we can see a new line with 'update-reducers'
Agreed.