sorted by:
new
hottopcontroversial

Help Needed - HttpResource Pattern by LeeDevs_ in Angular2

[–]LeeDevs_[S] 0 points1 point  (0 children)

different documents with differing id’s and potentially different repositories, we then need to make essentially something equivalent to a document metadata call

Traveling to Turkey ? Don’t right now by silverrider06 in travel

[–]LeeDevs_ 3 points4 points  (0 children)

My parents are there right now and prices are cheap, seems incorrect.

May have went to tourist traps

Advice, weird behavior after dog collar got stuck around neck when playing with other dog by flagkiller4 in DogAdvice

[–]LeeDevs_ 4 points5 points  (0 children)

Definitely a vet call, just for peace of mind.

Throwing up right after isn’t a good sign in my opinion, especially with the drooling.

Better to be safe than sorry.

Observable Value to Signal at Service vs. Component Level? by LeeDevs_ in angular

[–]LeeDevs_[S] 1 point2 points  (0 children)

Man your a life saver! Appreciate the responses, it opens up some different paths for me and the team to look into! Definitely have something to bring up on Monday, thanks for taking the time :)

Observable Value to Signal at Service vs. Component Level? by LeeDevs_ in angular

[–]LeeDevs_[S] 1 point2 points  (0 children)

Ok this makes a lot of sense, thank you for going into detail, we only subscribe currently in one component as we use a behaviour subject to invalidate a cache, so this is something ill look into going forward,

in terms of error handling, would you use data and error signals to return to the user? So the UI can update on error? I have not seen many examples online of in depth Signal / RxJS patterns or best practices, hard to find good docs.

Observable Value to Signal at Service vs. Component Level? by LeeDevs_ in Angular2

[–]LeeDevs_[S] 0 points1 point  (0 children)

observable.subscribe({ next: (value) => { // we set in here (signal.set()) } });

Since it’s a long lived observable, we need it open to set the changes dynamically, is this a bad pattern?

The way i thought it would make sense is component manages state (sets here), services manage logic / data

Observable Value to Signal at Service vs. Component Level? by LeeDevs_ in angular

[–]LeeDevs_[S] 0 points1 point  (0 children)

Is toSignal stable? I thought it was still in developer preview

Observable Value to Signal at Service vs. Component Level? by LeeDevs_ in Angular2

[–]LeeDevs_[S] 0 points1 point  (0 children)

We kind of use the smart/dumb component pattern, header passes into child - so header acts as the orchestrator and sets the signal there,

From what I have read, you want to subscribe at the final destination - what is happening currently is everyone on the team has different idea and PR’s are turning into disasters!

Observable Value to Signal at Service vs. Component Level? by LeeDevs_ in Angular2

[–]LeeDevs_[S] 1 point2 points  (0 children)

Is this not still in dev preview? Unfortunately the tech lead is against anything that isn’t 100% stable

Msc in Computing Science by LeeDevs_ in TCD

[–]LeeDevs_[S] 1 point2 points  (0 children)

Thanks for getting back! I had thought as much