In real angular APP, you do not use http observable directly, you want to use real data = TRUE/FALSE.
So if this should have been usable, you would have added support for TRUE/FALSE direct binding. :-(
[ngBusy]="booleanValue"
in normal production ready application, your components have never ever access to services, they have theirs INPUTs, like [loading]="value" and it is Boolean and it is taken from store (ngrx/redux anything).
From your services, you will just update boolean value in the store (for example with @ngrx/effects, or in normalne subscriptions).
Access services and subscriptions directly in your component is bad behavior and i think not to support it is your wish.
In real angular APP, you do not use http observable directly, you want to use real data = TRUE/FALSE.
So if this should have been usable, you would have added support for TRUE/FALSE direct binding. :-(
[ngBusy]="booleanValue"
in normal production ready application, your components have never ever access to services, they have theirs INPUTs, like [loading]="value" and it is Boolean and it is taken from store (ngrx/redux anything).
From your services, you will just update boolean value in the store (for example with @ngrx/effects, or in normalne subscriptions).
Access services and subscriptions directly in your component is bad behavior and i think not to support it is your wish.