As a happy owner of your course, it'll be my pleasure to read this nice update! Thank you Joshua for your dedication and for your high quality content 😊
Im partially reluctant to learn signals just because its taken so long for me to finally get used to rxjs haha. I guess ill have to make the leap at some point.
I can't recommend them highly enough; they're not too overwhelming to learn, and they make life so much easier and more responsive. Definitely worth the time investment to learn and start using them 👍
@@becom1ng it's not the difficulty of signals it's the amount of time I put into rxjs! It's hard to abandon something that was so difficult for me to start to feel at home with... 😅
Learning signals is not about getting rid of rxjs. The combination of both is what you want. Signals for state and observables for events. So I encourage you to go that route. It's worth it.
was close to finally learning rxjs and now this comes out, imo the frontend syntax is insane compared to spring for example which is more intuitive, I understand nothing from what Joshua is showing
Technically, is it possible to create a function or something else that allows you to have the functionality of a subject (action/event) and return a signal ? A new function in ngxtension Subgnal
Not really, you will run into the same fundamental issues once you convert it to a signal. If you have the Subject itself accessible, you can use that if necessary for events/actions. If you have some function that just returns a signal then it's the same problem where if you try to use that signal to react to events/actions then some may be missed.
@JoshuaMorony Having a function that returns both a Subject and its toSignal would be a game-changer for Angular developers. It would streamline the process of working with reactive data streams and provide a more consistent API for handling both Subjects and signals.
Question: in your LoginService why do you define a ‘login$’ subject and also define a corresponding toSignal? Why not just have the signal and set it directly?
This would actually work in this case, but the danger of using signal sets as a mechanism for "actions" is that they can miss actions/events due to the way effect scheduling works/signals not being designed for event handling generally. I'm not really 100% sure where I stand on this at this point, at the moment I'm leaning to using Subjects to represent all actions even though it isn't technically required in every case (I figure that's better than having surprising cases)
@@eneajahollari1203the current setup is far from ideal, in the React world with Vite the refresh happens in real time and maintains state, I really hope that the Angular team gives this issue the highest priority since it's a deal breaker for anyone who has used React
@@BenjaminFavre29 what am I missing with another framework? (Serious question, I decided not to flip about learning bits of all frameworks and just focussed on this one because back when I started it was the only one that ionic supported)
Join the newsletter: mobirony.kit.com/4a331b9076
As a happy owner of your course, it'll be my pleasure to read this nice update!
Thank you Joshua for your dedication and for your high quality content 😊
Joshua, your Angular course is amazing and the fact that you update it regularly is even better! 💪
I was a just about to have finished that course, seems like i have more work to do.. 😅
those changes are savage XD
Im partially reluctant to learn signals just because its taken so long for me to finally get used to rxjs haha. I guess ill have to make the leap at some point.
Same here... I saw so many videos from Joshua and when i finally lernt enough to work with RxJs, signals comes out...
I can't recommend them highly enough; they're not too overwhelming to learn, and they make life so much easier and more responsive. Definitely worth the time investment to learn and start using them 👍
Rest assured that Signals are incredibly easy compared to RxJS.
@@becom1ng it's not the difficulty of signals it's the amount of time I put into rxjs! It's hard to abandon something that was so difficult for me to start to feel at home with... 😅
Learning signals is not about getting rid of rxjs. The combination of both is what you want. Signals for state and observables for events.
So I encourage you to go that route. It's worth it.
was close to finally learning rxjs and now this comes out, imo the frontend syntax is insane compared to spring for example which is more intuitive, I understand nothing from what Joshua is showing
Currently working with angular 8 💀
why am I even here? 😭
Technically, is it possible to create a function or something else that allows you to have the functionality of a subject (action/event) and return a signal ?
A new function in ngxtension Subgnal
Not really, you will run into the same fundamental issues once you convert it to a signal. If you have the Subject itself accessible, you can use that if necessary for events/actions. If you have some function that just returns a signal then it's the same problem where if you try to use that signal to react to events/actions then some may be missed.
@JoshuaMorony Having a function that returns both a Subject and its toSignal would be a game-changer for Angular developers. It would streamline the process of working with reactive data streams and provide a more consistent API for handling both Subjects and signals.
Question: in your LoginService why do you define a ‘login$’ subject and also define a corresponding toSignal? Why not just have the signal and set it directly?
This would actually work in this case, but the danger of using signal sets as a mechanism for "actions" is that they can miss actions/events due to the way effect scheduling works/signals not being designed for event handling generally. I'm not really 100% sure where I stand on this at this point, at the moment I'm leaning to using Subjects to represent all actions even though it isn't technically required in every case (I figure that's better than having surprising cases)
Why the ominous soundtrack? ahaha
Still no fast refresh 😑
HMR should be there. For CSS and external templates, not inline ones.
@@eneajahollari1203the current setup is far from ideal, in the React world with Vite the refresh happens in real time and maintains state, I really hope that the Angular team gives this issue the highest priority since it's a deal breaker for anyone who has used React
v 19 is out and break all my tests and apps, it work fine in v 18, ng update no migrations
Why would anyone inflect angular on themselves at this point ?
@@BenjaminFavre29 what am I missing with another framework? (Serious question, I decided not to flip about learning bits of all frameworks and just focussed on this one because back when I started it was the only one that ionic supported)
Its hard to keep up with all the js frameworks lol, I rather go all in with Rust ... in front-end and backend... LOL