Signals are supposed to make Angular easy, what I see now as an experienced Angular Dev that Signals complicated Angular a lot. Even for me to get the interplay between Rxjs and Signals right is quite an endeavor. Rainer is an experienced Rxjs Dev he can do these twists but Angular Beginners will struggle a lot to need learn even more concepts than working with Rxjs only!
2 месяца назад+2
Can we get the source code of the example used in this workshop @RainerHahnekamp? I am interested in assertDefined(question) technic, thank you so much.
Hi! Thanks for such a great content, SignalStore is very powerful, but i cant figure out how to solve a complex scenario without using actions or without injecting all services inside the store. I'll try to create an example (a bit forced, but it's just to create some complexity). U have this function that takes a response to a quiz and validates it online, in base of response u have to interact with the UI and decide what to do: ``` 1. U submit a quiz response to an API
It's not the store's job to notify the user. You can keep the store focused on updating the state and have some sort of facade service that calls the store and then sends notifications. That way, such a service is never injected into the store. You don't want to tie UI features into business logic.
@@RomanMatkivskyy Yes, though it's not different from any regular Angular service. There are quite a few videos on the facade pattern with NgRx including this one from Rainer: ruclips.net/video/K4dpVXuhm14/видео.html
Signals are supposed to make Angular easy, what I see now as an experienced Angular Dev that Signals complicated Angular a lot. Even for me to get the interplay between Rxjs and Signals right is quite an endeavor. Rainer is an experienced Rxjs Dev he can do these twists but Angular Beginners will struggle a lot to need learn even more concepts than working with Rxjs only!
Can we get the source code of the example used in this workshop @RainerHahnekamp?
I am interested in assertDefined(question) technic, thank you so much.
Hi! Thanks for such a great content,
SignalStore is very powerful, but i cant figure out how to solve a complex scenario without using actions or without injecting all services inside the store.
I'll try to create an example (a bit forced, but it's just to create some complexity).
U have this function that takes a response to a quiz and validates it online,
in base of response u have to interact with the UI and decide what to do:
``` 1. U submit a quiz response to an API
It's not the store's job to notify the user. You can keep the store focused on updating the state and have some sort of facade service that calls the store and then sends notifications. That way, such a service is never injected into the store. You don't want to tie UI features into business logic.
@@AngularTraining it would be nice to have a video on the integration of this pattern with the new signalStore :)
@@RomanMatkivskyy Yes, though it's not different from any regular Angular service. There are quite a few videos on the facade pattern with NgRx including this one from Rainer: ruclips.net/video/K4dpVXuhm14/видео.html
very informative video, is the source code publicly available anywhere..?
I think this should be close enough: github.com/ngrx/signal-store-starter
github code?