-
Notifications
You must be signed in to change notification settings - Fork 19
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add an opt-in to call onError anyway #24
Labels
enhancement
New feature or request
Milestone
Comments
Note that this would require some reworking of internals to opt-in and allow it. Right now |
ZacSweers
added a commit
that referenced
this issue
Aug 17, 2019
This implements support for trying delegate onError calls if they opt in by implementing a new `TryOnError` interface. This will likely need to rely on guarded delegate call machinery, and need to figure out whether that should be another config or just supersede/defer to the existing config. Resolves #24
ZacSweers
added a commit
that referenced
this issue
Aug 21, 2019
This implements support for trying delegate onError calls if they opt in by implementing a new `TryOnError` interface. This will likely need to rely on guarded delegate call machinery, and need to figure out whether that should be another config or just supersede/defer to the existing config. Resolves #24
ZacSweers
added a commit
that referenced
this issue
Sep 15, 2019
* Implement TryOnError support This implements support for trying delegate onError calls if they opt in by implementing a new `TryOnError` interface. This will likely need to rely on guarded delegate call machinery, and need to figure out whether that should be another config or just supersede/defer to the existing config. Resolves #24 * Split reportError and createError * Add DeliverModifiedException marker type * Update observers for new DeliverModifiedException API * Rename new marker interfaces TryOnError -> RxDogTagErrorReceiver DeliverModifiedException -> RxDogTagModifiedExceptionReceiver * Rename new marker interfaces TryOnError -> RxDogTagErrorReceiver DeliverModifiedException -> RxDogTagModifiedExceptionReceiver * Spotless * Spotless
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This way, if someone supplies their own
LambdaConsumerIntrospection
, they could control this behavior if they want (such as if theirs just logs an error)The text was updated successfully, but these errors were encountered: