Fix Exception vs Throwable typo#173
Merged
benjchristensen merged 1 commit intoNetflix:masterfrom Aug 20, 2013
benjchristensen:fix-exception-throwable-typo
Merged
Fix Exception vs Throwable typo#173benjchristensen merged 1 commit intoNetflix:masterfrom benjchristensen:fix-exception-throwable-typo
benjchristensen merged 1 commit intoNetflix:masterfrom
benjchristensen:fix-exception-throwable-typo
Conversation
- This was using the Object overload rather than statically typed Func1<Throwable> method. This was caught when testing RxJava 0.11.0 which restores static type safety.
benjchristensen
added a commit
that referenced
this pull request
Aug 20, 2013
…typo Fix Exception vs Throwable typo
|
Hystrix-pull-requests #44 SUCCESS |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This was using the Object overload rather than statically typed Func1 method. This was caught when testing RxJava 0.11.0 which restores static type safety.
See ReactiveX/RxJava#319 for more information.