You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is more of a question than a bug report. Using the ngIf hack you can do this sort of in your component templates to be able to use 2+ observables in multiple places within your template.
<ng-container
*ngIf="{
hasSelections: (screenManager.hasSelections$ | async),
isSaving: (screenManager.isSaving$ | async)
} as vm"
>
... code here
</ng-container>
Questions:
Are you able to use @rx-angular/template to do something like this, with all of the performance gains of the library still in tact? Keeping in mind that there are some pages where I have 8+ observables, I don't want to have to do an *ngLet for each one.
If yes, how would you structure it?
The text was updated successfully, but these errors were encountered:
Hey, I just wanted what the correct way to this now would be. Is it still the accumulateObservables operator? I was wondering, because it is in the internales/core package.
If this cart template which needs promotions, prices and allocations:
Description
This is more of a question than a bug report. Using the ngIf hack you can do this sort of in your component templates to be able to use 2+ observables in multiple places within your template.
Questions:
The text was updated successfully, but these errors were encountered: