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
Currently, there are operators like retryWhen that allow replacing the Context in the user's code. It is error prone and does not seem to have valid use cases (to be validated)
Desired solution
Instead of replacing, user-provided Context should always be merged into the current one.
Currently, only retryWhen is considered, but we should check whether there are other operators that allow user-provided functions replace the Context.
Note that if the companion Publisher created by the whenFactory emits Context as trigger objects, these Context will REPLACE the operator's own Context. Please be careful there: replacing the Context means that some keys you don't own could be removed, breaking libraries that depend on them.
The text was updated successfully, but these errors were encountered:
Motivation
Currently, there are operators like
retryWhen
that allow replacing theContext
in the user's code. It is error prone and does not seem to have valid use cases (to be validated)Desired solution
Instead of replacing, user-provided
Context
should always be merged into the current one.Currently, only
retryWhen
is considered, but we should check whether there are other operators that allow user-provided functions replace theContext
.Considered alternatives
TBD
Additional context
https://projectreactor.io/docs/core/release/api/reactor/core/publisher/Flux.html#retryWhen-java.util.function.Function-
The text was updated successfully, but these errors were encountered: