SIGNALS can make Angular "REACTIVE" forms more reactive 

Glad you're finding them useful!

What are your problems with reactive forms?

The plan currently is to wait for signal based components and then I'll update everything to that, but mostly there isn't much to update just the extra things that came after the v17 release

@@JoshuaMorony youre right, its better to wait, thank you for everything! I wish you had more angular project oriented courses 😉

Hey thanks Robin, definitely keen to dive into some more ideas here so I'll check it out for sure

Any effect will execute any time any of the signals it references change (and also once initially which is why the init effect works)

I've only briefly seen bits and pieces so not enough to comment, and in general I just haven't given template driven forms a proper go yet - I've felt for a long time now that I probably would like template driven forms, but the opportunity to try it out properly just hasn't eventuated

At a glance I would think this should be fine - auto applying some previous selected options would likely look similar to what I have in the video, maybe disable the form in the init effect, and load the necessary data as a source + have a side effect via tap to set the data. Then for reacting to changes you might have something like my "requireExplanation" effect, you have all of your form control values available as signals via the selectors, so you can create an effect that runs whenever a particular control value changes - from that effect you should be able to trigger an "actionSource" which can make the call to load the models for that make, and potentially have an "actionEffect" that runs when that "actionSource" emits to handle setting the data in the form + resetting the model back to null. This is all off the top of my head of course so it might require some playing around with - if you do end up trying it and run into any issues feel free to let me know.

Agreed and as I mentioned in another comment I don't really see this particular approach as a solution to forms generally, I think a more targeted/specific solution will be better. But for people who are using signalSlice or some approach that works similarly, this could be a nice way to integrate into existing patterns (and then maybe when better patterns come along, state management approaches like signalSlice might just integrate into those instead)

yes thanks, I'll have try and see if that works here instead of disabling emitEvent (not actually sure since the signal set is being triggered by the valueChanges observable updating)

I don't have much to add on outside of what's in the video, but I do find value in having the signalSlice handle all sources of state and being able to derive/react to whatever I need through that - the form submission being a good example of the way it can make things more declarative. As I mentioned though I don't think this is the best abstraction that we can land on specifically for managing forms - signalSlice serves other purposes and happens to integrate in a reasonably convenient way with reactive forms without needing to bring in some other abstraction. I wouldn't advocate for signalSlice as a way to manage forms specifically if you aren't already using it for state management.

Why?

@@Framoio is very simple and clear the reactive forms

I just did actually, hopefully this is more to your liking: ru-vid.com/video/%D0%B2%D0%B8%D0%B4%D0%B5%D0%BE-H6fQB9hMUCU.html