Learn NgRx Component Store - Local Store With NgRx

[@MonsterlessonsAcademy]

WATCH NEXT: Angular with NgRx - Building Angular Project From Scratch - kzbin.info/www/bejne/rJTJi2N7htWMiqMsi=BptT7eqgflHIoQiQ

[@returncode0000]

Your videos always help me a lot because you always provide very good explanations for difficult topics, thanks!

[@MonsterlessonsAcademy]

Thank you so much for your support. It means a lot to me!

[@Jerokun]

Straight to the point with a clean solution. If you are reading up on Component Stores and want to know if it's the right fit for you, this video gives you a good practical example for you to make your decision. Thank you for this! Still looking to see how to I can combine this with NGRX Data to reduce boiler plating.

[@MonsterlessonsAcademy]

You are welcome!

[@eva_space]

Thanks a lot for information. It's really great solution.

[@MonsterlessonsAcademy]

You are welcome!

[@williamxsp]

Very good content. Easy and simple to get through. Thanks

[@MonsterlessonsAcademy]

Glad it was helpful!

[@Ald0Abdiel]

Amazing video teacher thanks, but I have one question or rather two. One thing that I really like of the global store is the dev-tools which allows to see step by step the actions made by the users, but for the component store I couldn't find it inside the devtools, is this intended? if so what's the best way to debug or rather see the actions that the user does with the component-stores. Another question I have is regarding how to decide when to use component store or global store? in the context of a big project with NX that will host within multiple apps, what would be the best practice approach; is it important for me to worry about component-store or would be best if I only end up using the global store? Thanks again for the great content.

[@MonsterlessonsAcademy]

This is why I don't like component store and mostly use global store. Because of devtools which are not available for comp store. There is not a single best practice, just use what fits you and your application. Comp store are fully isolated with the comp and global store not.

[@BonBiBon]

Cooooooool!

[@MonsterlessonsAcademy]

Thanks

[@andrsbrbs]

I have one question: by providing PostsStore to the component directly, each component will have its own store instance, right? Just like with services without using { providedIn: 'root' } and providing it on the component itself?

[@MonsterlessonsAcademy]

It's an alternative to reactive push-based "Service with a Subject" approach. So you can access it from different components like a service

[@Serialloserr]

1 like is not enough. Thanks alot

[@MonsterlessonsAcademy]

You are welcome!

[@JohnSmith-yr7ih]

Please explain: why is this needed at all? Is it used often in real projects? If so, why?! It's just extra code for nothing

[@MonsterlessonsAcademy]

It is not mandatory but it helps to organize your local stage. Here is a comparison with ngrx state ngrx.io/guide/component-store/comparison