Redux modules for the Features, not for Domains/Entities

[dzintars]

It is wrong to think in terms of Domains/Entities when creating Redux module. Quite soon you will end up with the situation, when you want to combine slices from the different modules.
Instead you should think in terms of Features. For example, i have this app-navigation component (so called - Feature). This components simply displays list of the modules for the given application. So, we need an application ID to get its module id's and then the rest of the data for the every module.
This means we should hit 2 API endpoints to combine this data.
Don't forget also about the data normalization.
So, this seems a good case to implement app-navigation module in Redux. And it helps to maintain decoupling.

[dzintars]

I created API method to request all required data at one go.
dzintars/wss@24e448e
dzintars/wss@5959732

This seems could work. For sure its quick and dirty, but the general idea is like that. Pass the app ID and get all the modules.

[dzintars]

Still need to play with this "ideology" for some time to feel comfortable with it.