Is this how we will handle errors reactively with signals in Angular?

I would love to start a discussion about the usage of services in the template. I am probably old school and would argue that everything injected should be private and therefor not directly accessible in the template

About your video - I really like the thoughts and approach you've taken and would currently also tend to go that route

I like this approach that you mention :)

This approach is nice. I like it

Nice approach, clever 👍

Your solution is a little bit like a "Result" in Rust. Looks nice.

why did you switch to neovim?

And what about a retry-button for example. After it the rxjs-stream (getFromApiError()) errors, isn't it "dead"? how would you go about implementing a retry which results are delivered in the same rxjs stream?

How to manage with this package the case of different error management in a stream who includes multiple call trough switchMap operator ? Like if something, stop the calls and display a banner, if something else retryWhen operator ?

You are a legend, mate. Any plans for a promotion of Ionic Start? Help your fellow Brazilians lol

You lost me at of(null)...

Getting kind of async/await/promise handling vibe from this. :)

Clean intuitive approach. I see this becoming a common practice.

Always qualitative and well explained stuff ! Thanks a lot !

Love this approach!

Isn't there a drawback to this approach if you want to show the data and the error at the same time? For example if you have already fetched your data once and then an error occurs the second you fetch your data, value will be undefined. Therefore you won't be able to display your data and the error simultaneously.

This is a good video and nice explanation.

Creating a NPM package for 20 lines of code that can easily be copy-pasted is everything that's wrong with the JS ecosystem though :D

I love the approach! Its basically the Either<Success, Error> pattern in a reactive way :) the helper function should make writing stuff like this much easier.

Very nice way of keeping things reactive as they evolve ! thank you !

Pretty clean pattern I think ! Nice catch 🙂

I like the approach! Very clean and straight forward. Thanks! Do you know if we need to unsubscribe a long running observable inside a toSignal function?

This is a pattern that I have been using for quite some time and it's pretty handy. You can also use materialize operator instead of map + catchError.

I think it's a neat approach. Will test today. 😊

yur method do not work with update, mutate etc. it is fail

I used similar structures before signaljs was a thing. Not for signaljs but more for fellow developers having a hard time reading rxjs pipes.

Nice Joshua! Thanks

Clean approach!. I want to ask how do you handle for mutation request that can be called multiple times using signal?

Like your video. Good approach but one thing is not clear if I have to pass ToSignalOptions like initialValue, requireSync etc. this is not possible with your utility function