Don't make my toSignal mistake in Angular

[@JoshuaMorony]

Join the weekly newsletter: mobirony.ck.page/4a331b9076

[@moitp2]

I am not sure to understand why this is not set by default tbh

[@dev_bits]

This kind of tips what the developers need. Thanks.

[@StephenMoreira]

Short and sweet, thanks for the tip.

[@andresmauriciofajardoolaya2721]

Thanks for the content Joshua

[@dinysanchez]

Thanks Joshua!

[@DorianDauphin]

Thanks for the content, Joshua. In a previous video, you stated that we should use Signal for synchronous tasks and RxJS when dealing with asynchronous tasks, but this still isn't very clear to me. It would be nice if you could make a video with simple examples showing when it is more appropriate to use signals over RxJS, or vice versa. Have a good day !

[@valsimot-pod-dunavom]

great video, thanks for the info :D

[@g-luu]

Great one thanks

[@trevormontgomery6795]

I think this might be my problem in something I'm working on. I was getting what seems like a recursion error when I make an http call. An error must be occurring and angular things I've got a recursive function

[@shreyanshjain9479]

That's really cool trick❤

[@ianokay]

Very useful information from the cutting edge, nice video thanks. Unfortunate that it seems you have to spam every toSignal in your application with that object property if you want centralized error handling.

[@JoshuaMorony]

I suppose you could also write a little helper utility if you wanted to have it by default everywhere

[@PavelKostenko]

What code editor are you using, is this nvim inside tmux? Please share your setup

[@JoshuaMorony]

Yes it is - this video is somewhat old but covers most of what I am using: kzbin.info/www/bejne/hma0gZSZr5dgl9E I do have a couple other videos I think that talk about various aspects of my workflow/neovim setup

[@anon5992]

how can we utilize @error with this approach?

[@richardscholten100]

Why Is It When Something Happens, It's Always You RxJS? Thanks, exactly the problem i was facing...

[@christianhalaby832]

do you think not using signals at all is a set back?

[@svenson95]

I don't really understand what you're doing in 1:50, the as const suffixes. What is happening there? it seems like the status property (a string) gets transformed to a variable / constant. I've never seen this before.

[@RodrigoSalesSilva]

by default if you set a string to any variable the type will be infered as string, but if you use as const the type will be infered as the exact string, like "let a = 'authenticated' as const" the type of "a" will be infered as 'authenticated', otherwise it would be 'string'.

[@svenson95]

@@RodrigoSalesSilva okay interesting, but what is the benefit of having this status property not as type string but the actual value? In the next slide (2:01) we're just checking if the status value is "error", if i'm not wrong. Sorry if this is obvious, i feel kind of stupid right now :D

[@JoshuaMorony]

​@@svenson95 this stream needs to return status values that match a union type of "initial | authenticating | authenticated | error", if I return just "error" for example it won't let me do that because type "string" is not assignable to that union type. If I use "as const" the specific string "error" does match that type.

[@sergiokagiema9658]

Where are the 4 reads that procude 4 triggers ?

[@JoshuaMorony]

I think in the example the signal value is only actually referenced once, but it will depend on how many times change detection is triggered - so even if you only accessed the signal once in the template, but CD ran 4 times, it would cause 4 reads

[@sergiokagiema9658]

I see, I got it! Thanks for clarifying it!

[@leolanese]

...{rejectErrors: true} nice 👍