Sometimes is needed to access to a value from an observable, let’s say I have a selector

public getUser$: Observable = this.store.select(state => state.user)

And I need the value that comes from that observable to validate some variables into my .ts controller, it is posible to AVOID in the .ts subscribing to that observable to get the value?, because is a value that I’ll not use in the template (so i can not use async pipe),


private user: User = {} as User;
(...)
private anyName(): void {
this.facade.getUser$.subscribe((user: User) => {
this.user = user;
})
}


Doing the code above is bad? in the case that I need the information from the observable to be handled and used in the .ts, not in the template.

I got a little bit confused

Thanks!

Sure.

Lets say
1. a component with 6,7 buttons.
2. each of these buttons will trigger different http verbs (http put, post or delete) to maybe different url.
3. all the differernt request of these http calls all need to be composed with maybe the response of one single http.get call.

Thank you.

Thanks!

That is why I wrote the second scenario:
As parameters to function/HTTP calls

And how you should handle that 🙂

I still don’t recommend you to use state properties as you are loosing the powers of the reactive architecture as stated in the article. Do you have a good example where this would make sense?

That is why I stated there are exceptions but subscribing in the template using async pipe is the general best practice for reactive Angular apps as it is the least boilerplate and it will automatically unsubscribe eg. selectors.
Of course there are exceptions as I wrote:
”
We want to avoid manually calling subscribe as much as possible but there are still cases, where it makes sense to manually subscribe. Common scenarios are subscribing to a FormControl’s valueChanges or router events. But in all other cases, we want to just follow the two cases above.
“

Yes, that is exactly what I said.

The point is to keep the value in the stream until the end destination. Most commonly in an NgRx setup that would be either in the template (using async pipe) or in an effect (using withLatestFrom). That is the most common cases. I know there are exceptions, as the one I stated in the article, but as a general guideline, this will save you from a lot of pain 🙂

I think, you are really working against the observable pattern when you map to a state property.
As soon as it is out of the stream, you need to handhold imperative code and lose the reactive control which will save you from bugs and race conditions.
Can you explain an example, where you think a state property would be appropriate?