Add methods to determine cause of APIException#310
Merged
jimmyjames merged 3 commits intomasterfrom Oct 28, 2020
Merged
Conversation
lbalmaceda
previously approved these changes
Oct 27, 2020
Contributor
lbalmaceda
left a comment
lbalmaceda
left a comment
There was a problem hiding this comment.
Left one comment, not a blocker
lbalmaceda
approved these changes
Oct 28, 2020
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.
Changes
Resolves #279.
Adds methods to
APIExceptionto help determine the cause of the underlyingAPIException, similar to howAuth0.Androidhandles this. Other methods can be added in the future as needed.References
Testing
There is no existing test for
APIException; this change adds a test class but only adds tests for the added functionality.Checklist