Add NotFoundError to simplify exception handling #24
Conversation
This file contains 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
morgangallant
approved these changes
May 22, 2024
Comment on lines
+18
to
+22
| def raise_api_error(status_code, status_name, message): | ||
| if status_code == 404: | ||
| raise NotFoundError(status_code, status_name, message) | ||
| else: | ||
| raise APIError(status_code, status_name, message) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Currently there are a few methods that are expected to 404 in cases that a user might want to catch and ignore. At the moment the code for that is quite verbose since it's required to check for the status code on the APIError type
This PR exposes a new NotFoundError type that can easily be caught.