-
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 option to disable guarded delegate call #43
Conversation
* during observer callbacks are intercepted and routed to RxDogTag's error handling that | ||
* will give you more info on the subscription point. Set to true by default. | ||
* @return this builder for fluent chaining. | ||
* @see #guardedDelegateCall(NonCheckingConsumer, Runnable) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Let's not point to internal APIs
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good point
f0bb0a3
@@ -213,6 +213,26 @@ public void repackagingOENIEs_disabled() { | |||
assertThat(cause.getStackTrace()[1].toString()).contains(RxDogTag.STACK_ELEMENT_SOURCE_HEADER); | |||
} | |||
|
|||
@Test | |||
public void guardObserverChecks_disabled() { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can you explain how this tests guarded delegate calls? I don't see a delegate implemented here that would throw
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It actually doesn't. It's just a sanity check to make sure that even if we disable guarded delegate calls, our normal workflow works correctly. It's basically checking the if-else
statement in the DogTag*Observers
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Let's name or comment this to make that clear
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM. Go ahead and merge and I'll rebase #41 separately
Resolves #20
Might have to wait for #41 to merge and i can rebase with the newer benchmarks.
Posting newer benchmarks:
Event throughput: grouped by number of events:
Subscribe cost: grouped by complexity:
E2E amortized cost: