always in pull/paused/consuming mode (cf. Flowable)
hot if there is at least one subscriber (not represented in the typing)
This is an interface to ease the use of RxJS pipe operators and utilities
like EMPTY. However note that some (e.g. from and merge)
may create misbehaving consumables that flow with incorrect backpressure.
Note that a consumable is generally more prone to resource leaks than a
typical observable, because resources may be held open while waiting for
backpressure to be relieved by a call to {@link Bite.next()}. Such leaks
can even occur if the consumable is never subscribed, because of pre-emptive
actions taken when it was created, prior to the first consumer/subscriber.
the function that is called when the Observable is
initially subscribed to. This function is given a Subscriber, to which new values
can be nexted, or an error method can be called to raise an error, or
complete can be called to notify of a successful completion.
Creates a new Observable, with this Observable instance as the source, and the passed
operator defined as the new observable's operator.
method
lift
deprecated
Internal implementation detail, do not use directly. Will be made internal in v8.
If you have implemented an operator using lift, it is recommended that you create an
operator by simply returning new Observable() directly. See "Creating new operators from
scratch" section here: https://rxjs.dev/guide/operators
Instead of passing separate callback arguments, use an observer argument. Signatures taking separate callback arguments will be removed in v8. Details: https://rxjs.dev/deprecations/subscribe-arguments
A consumable is an observable that is
This is an interface to ease the use of RxJS pipe operators and utilities like
EMPTY. However note that some (e.g.fromandmerge) may create misbehaving consumables that flow with incorrect backpressure.Note that a consumable is generally more prone to resource leaks than a typical observable, because resources may be held open while waiting for backpressure to be relieved by a call to {@link Bite.next()}. Such leaks can even occur if the consumable is never subscribed, because of pre-emptive actions taken when it was created, prior to the first consumer/subscriber.
Bite