74

Hi I have a observable user$ with a lot of properties (name, title, address...)

component{
  user$:Observerable<User>;
  constructor(private userService:UserService){
    this.user$ = this.userService.someMethodReturningObservable$()
  }
}

Is there a way to use the async pipe in the html template to subscribe to it and bind it to a local variable like this

<div #user="user$ | async">
  <h3> {{user.name}}
</div>

I know can can subscribe to it in the constructor and then unsubscribe in OnLeave/OnDestroy but I was just curious if I could use the async pipe.

Cheers

2
  • As I know async pipe only works with *ngFor ? in that you can do this *ngFor="let u of (user = (user$ | async))" but seems fishy. need a bit practical. Commented Apr 10, 2017 at 14:38
  • not async can work on a single observable as well, see ngrx/store :) Commented Apr 10, 2017 at 14:46

5 Answers 5

161

# is template reference variable. It defers to DOM element and cannot be used like that.

Local variables aren't implemented in Angular as of now, this closed issue can be monitored for the references to related issues.

Since Angular 4 the syntax of ngIf and ngFor directives was updated to allow local variables. See ngIf reference for details. So it is possible to do

<div *ngIf="user$ | async; let user">
  <h3> {{user.name}} </h3>
</div>

This will create div wrapper element and will provide cloaking behaviour to it, so there's no need for ?. 'Elvis' operator.

If no extra markup is desirable, it can be changed to

<ng-container *ngIf="user$ | async; let user">...</ng-container>

If cloaking behaviour is not desirable, the expression can be changed to truthy placeholder value.

A placeholder can be empty object for object value,

<div *ngIf="(user$ | async) || {}; let user">
  <h3> {{user?.name}} </h3>
</div>

Or a space for primitive value,

<div *ngIf="(primitive$ | async) || ' '; let primitive">
  <h3> {{primitive}} </h3>
</div>
Sign up to request clarification or add additional context in comments.

7 Comments

This is working for me, however I'm getting a warning saying 'of' expected. I think this is a tslint warning, but having a hard time finding any info for it.
@Blexy It's hard to say what's wrong here, it looks like a part of some message.
Yeah I'm getting the same error with the 'of' expected, I was trying to reform it so it would make sense to both the linter and Angular, but that turns out to be a bit harder then expected. Feels like some automagic with the async pipe.
@BjornSchijff did you identify a workaround for 'of' expected?
@Blexy You didn't mention that this is IDE warning, in fact. TSLint doesn't care about templates.
|
44

@Bjorn Schijff and @estus

Instead of:

<div *ngIf="(user$ | async) || {}; let user">

Do:

<div *ngIf="(user | async) as user">

6 Comments

Yes, I have angular 4.4.3
Both as and let are supported by the framework. Why exactly should it be done this way and not another?
I have no idea, it worked with angular 4.4.3. Maybe both works with angular 5.
Example given by @WooliDesign works, here is the doc link for ref
You'll get unresolved variable error in Angular 8 by doing so.
|
9

Use following syntax:

<div *ngIf="(user | async) as user"> 

Note: The addition of “as user” at the end of the expression.

What this will do is wait until user$ | async has evaluated, and bind the result to the value of user (non-dollar-suffixed).

1 Comment

How is this any different from @WooliDesign's answer?
1

For *ngFor it's possible with added *ngIf directive on parent element:

    <ul *ngIf="users$ | async as users">
      <li *ngFor="let user of users">{{user.name}}</li>
      <li *ngIf="!users.length">No users</li>
    </ul>

If there's already a structural directive on the parent element, then introduction of an intermediate element like <ng-container> may be necessary.

Comments

1

For the versions of angular 17+, the new syntax is like so:

@if(user$ | async; as user) {
    <h3> {{user.name}} </h3>
}

Comments

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.