public final <R> Mono<T> doOnDiscard(final Class<R> type, final Consumer<? super R> discardHook) {
    """
	Modify the behavior of the <i>whole chain</i> of operators upstream of this one to
	conditionally clean up elements that get <i>discarded</i> by these operators.
	<p>
	The {@code discardHook} must be idempotent and safe to use on any instance of the desired
	type.
	Calls to this method are additive, and the order of invocation of the {@code discardHook}
	is the same as the order of declaration (calling {@code .filter(...).doOnDiscard(first).doOnDiscard(second)}
	will let the filter invoke {@code first} then {@code second} handlers).
	<p>
	Two main categories of discarding operators exist:
	<ul>
	<li>filtering operators, dropping some source elements as part of their designed behavior</li>
	<li>operators that prefetch a few elements and keep them around pending a request, but get cancelled/in error</li>
	</ul>
	These operators are identified in the javadoc by the presence of an {@code onDiscard Support} section.
	
	@param type the {@link Class} of elements in the upstream chain of operators that
	this cleanup hook should take into account.
	@param discardHook a {@link Consumer} of elements in the upstream chain of operators
	that performs the cleanup.
	@return a {@link Mono} that cleans up matching elements that get discarded upstream of it.
    """
		return subscriberContext(Operators.discardLocalAdapter(type, discardHook));
	}
public final <R> Mono<T> doOnDiscard(final Class<R> type, final Consumer<? super R> discardHook) {
		return subscriberContext(Operators.discardLocalAdapter(type, discardHook));
	}
public final < R > Mono < T > doOnDiscard ( final Class < R > type , final Consumer < ? super R > discardHook ) { return subscriberContext ( Operators . discardLocalAdapter ( type , discardHook ) ) ; }
Modify the behavior of the <i>whole chain</i> of operators upstream of this one to
conditionally clean up elements that get <i>discarded</i> by these operators.
<p>
The {@code discardHook} must be idempotent and safe to use on any instance of the desired
type.
Calls to this method are additive, and the order of invocation of the {@code discardHook}
is the same as the order of declaration (calling {@code .filter(...).doOnDiscard(first).doOnDiscard(second)}
will let the filter invoke {@code first} then {@code second} handlers).
<p>
Two main categories of discarding operators exist:
<ul>
<li>filtering operators, dropping some source elements as part of their designed behavior</li>
<li>operators that prefetch a few elements and keep them around pending a request, but get cancelled/in error</li>
</ul>
These operators are identified in the javadoc by the presence of an {@code onDiscard Support} section.

@param type the {@link Class} of elements in the upstream chain of operators that
this cleanup hook should take into account.
@param discardHook a {@link Consumer} of elements in the upstream chain of operators
that performs the cleanup.
@return a {@link Mono} that cleans up matching elements that get discarded upstream of it.
Modify the behavior of the <i > whole chain< / i > of operators upstream of this one to conditionally clean up elements that get <i > discarded< / i > by these operators . <p > The { @code discardHook } must be idempotent and safe to use on any instance of the desired type . Calls to this method are additive and the order of invocation of the { @code discardHook } is the same as the order of declaration ( calling { @code . filter ( ... ) . doOnDiscard ( first ) . doOnDiscard ( second ) } will let the filter invoke { @code first } then { @code second } handlers ) . <p > Two main categories of discarding operators exist : <ul > <li > filtering operators dropping some source elements as part of their designed behavior< / li > <li > operators that prefetch a few elements and keep them around pending a request but get cancelled / in error< / li > < / ul > These operators are identified in the javadoc by the presence of an { @code onDiscard Support } section .