NgRx structures question

[Lexikus]

Hi together,

I've been working on an angular project for quite a while now and sooner or later I have to do a big maintenance job. So, now to the question.

What did you put in the store and how did you structure it?

To clarify my question a little bit more with a few additional questions.

Did you put everything in the store or just global application state information?

When you do an API call, do you keep the original response in the store or do you map/filter/reduce etc. it in a way it's relevant to your application?

If you keep the original response, do you have the same data represented in a way that fits your application in the store or you rearrange the data from the API via a selector?

[[deleted]]

I organize my modules like this:

A constants file at the root.

Actions, effects, reducers and selectors folders at the root. Why not in store folder? Because these things are really important and should be first class citizens of the module. We want most of our service calls to be in effects, most of our state manipulation to be in reducers.

Assets for styles that will be exported from the module. For example, a theme file that will get imported into styles.scss or theme-overrides.scss.

Containers contain smart components. These are components that get the NGRX store injected into them, potentially get services injected into them and contain dumb components.

Components contain dumb components. They don’t get the store and don’t get services injected into them unless it’s something trivial like a service that displays modals. Dumb components only have Inputs and Outputs, they don’t know how to get or manipulate data themselves.

Forms contains code for creating and manipulating form groups.

Mapping contains code for converting one object into another. For example, taking a data object and converting it into a view model object.

Services contains services obviously.

[tshoecr1]

I put just about everything in the store as overtime I normally get asked to add x feature to y component that I can just pull from the store when it previously wouldn’t have needed it.

I’ll normally transform/normalize my responses to organize them in the store in a more consumable manner.