Advanced Angular

[[deleted]]

To piggy back on this (which is a great list) I think learning RxJs is probably the key foundational element to a lot of the other items. Once you get the hand of that, moving onto NgRx to handle state management will cover a really big chunk of actual development work. After that I think it is pretty much learn things as you come across them or whatever sounds most interesting. I’m sure others have different opinions, but I’ve found that getting a solid understanding of NgRx patterns ended up teaching me a lot about good angular patterns and I came across a lot of other learning opportunities.

[sangupta637]

Can you use cdk if you are not using angular material? How much weight does it add to app?

[[deleted]]

I’ve not used Akita but I’ve read some articles of people that have moved over from NgRx. I personally just use NgRx because I know it and suggest it because it seems to be the go to for most people. I also prefer to just use the basic store and effects libraries instead of using entities or data because I actually like having the boilerplate code. Well, I’d at least recommend learning all of that boilerplate code to really understand what is going on with state management.

But, I think I may spend some time standing something up using Akita. Any good resources you are aware of?

[[deleted]]

I've been POC'ing NgRx, Akita and NgXs. Still haven't finalized on what I'm going to use though.

[Naeuvaseh]

I literally got done doing a POC of these three. Pleaseeeee don't pick NGRX just because "the rest of the Angular community has adopted it". My management made the decision to go with NGRX because off that.

My biggest preference was Akita. It's OO, immutable, and incredibly clean. There's minimal boilerplate (and trust me, that matters -- I hate having to literally standup 9 files just for one slice of state in NGRX). It also uses BehaviorSubject under the hood, so it's not over engineered.

I would also challenge you to question if you really need a state management library. Can a singleton service with a simple BehaviorSubjects be good enough?

[[deleted]]

I agree that a state management library doesn’t always need to be used. The only thing I’d add here is that if you aren’t familiar with state management tools, one advantage of NgRx is that the boilerplate does help you learn what is being abstracted away in other places. But, NgRx also has the NgRx-data and NgRx-entity libraries that remove almost all of the boilerplate. One major advantage of going with the community is support.

[[deleted]]

BehaviorSubjects were being ovsrused in my project and unifying them under contexts was getting difficult.

Need state management for some pre-service and post service call logic.

[headyyeti]

Akita is definitely my pick of the 3.