Can you please shed some light on how future looks with NGRX(Included Entities) + Signals, are we going to discard using NGRX and solely depend of Signals or can we still do state management with NGRX along with Signals. As always thanks for making an awesome content.
That's a great question which I looked for myself as I want to update my Angular/NgRx course and make it with correct choices :) So Signals will be dominant together with standalone components (and full projects). In NgRx github core contributors wrote that they will use signals under the hood with no changes from ngrx state packages. Additionally they will make ngrx signals package similar to ngrx component store which will be limited to a single component.
I am worried about the future of NGRX store, because the introduction of signal, this library is highly built on top of RXJS and depends a lot ot it, and with the new signals api i dont't see where this fits on... I've been using NGRX store for so long and i like it.
I already replied such concerns. That's a great question which I looked for myself as I want to update my Angular/NgRx course and make it with correct choices :) So Signals will be dominant together with standalone components (and full projects). In NgRx github core contributors wrote that they will use signals under the hood with no changes from ngrx state packages. Additionally they will make ngrx signals package similar to ngrx component store which will be limited to a single component.
Hi, I've stucked with problem, I have a big object and there is a nested array of objects in it, how can I updated nested object in this array and in the result I want that my selector fired an event into the stream to updated template with new Data ?
WATCH NEXT: Angular with NgRx - Building Angular Project From Scratch - th-cam.com/video/vcfZ0EQpYTA/w-d-xo.htmlsi=BptT7eqgflHIoQiQ
Great video, your video explained what is that and the behaviors of this tool 🎉.
Glad it was helpful!
Great video, thx ! :)
Glad you liked it!
Can you please shed some light on how future looks with NGRX(Included Entities) + Signals, are we going to discard using NGRX and solely depend of Signals or can we still do state management with NGRX along with Signals. As always thanks for making an awesome content.
That's a great question which I looked for myself as I want to update my Angular/NgRx course and make it with correct choices :)
So Signals will be dominant together with standalone components (and full projects).
In NgRx github core contributors wrote that they will use signals under the hood with no changes from ngrx state packages.
Additionally they will make ngrx signals package similar to ngrx component store which will be limited to a single component.
@@MonsterlessonsAcademy thanks for quick reply I really appreciate it. I will be looking forward to your course with Angular + Signals.
Greate video, thank you
You are welcome!
Could you increase you current course of ngRx with a chapter about ngrx entity? Great video by the way!
I plan on full updating my angular ngrx course so will see
Yes, please update your ngrx course. Thanks
@@felixmatusinio6438 It is already recorded. I'm editing it now and will update on all platforms really soon.
@@MonsterlessonsAcademy That's great. Thank you so much
Please explain: why do you use here `selectors-ts` file? can't we simplify it with `Create Feature`?
Sure. Go for it.
Could you please create a video tutorial explaining how to utilize multiple EntityState and Adapter in a single state file?
I will add it to the list of future videos
I am worried about the future of NGRX store, because the introduction of signal, this library is highly built on top of RXJS and depends a lot ot it, and with the new signals api i dont't see where this fits on... I've been using NGRX store for so long and i like it.
I already replied such concerns.
That's a great question which I looked for myself as I want to update my Angular/NgRx course and make it with correct choices :)
So Signals will be dominant together with standalone components (and full projects).
In NgRx github core contributors wrote that they will use signals under the hood with no changes from ngrx state packages.
Additionally they will make ngrx signals package similar to ngrx component store which will be limited to a single component.
Sorry if the question is silly. If store would be provided lazily would it be in component provider or route provider
You can do both. depending on your needs.
Hi, I've stucked with problem, I have a big object and there is a nested array of objects in it, how can I updated nested object in this array and in the result I want that my selector fired an event into the stream to updated template with new Data ?
{...state, nested: {...state.nested, newprop: 'newprop}}
which one to choose? ngrx entity or createFeature
These are 2 completely different things. createFeature is sugar for reducers and selectors. ngrx entity is a sugar to work with lists of entities.
I feel that Entities is an overkill. It adds quite more codes with steeper learning curves for things that could be easily done
Yeap, I don't like/use them either