upgrade paginator error handling for response JSON conversion #309
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.
Description
if there is an issue while converting the API response to JSON, then I am assuming that there has been an error and the server has returned something that was not JSON (e.g. text) where JSON was expected, so there must be an error, thus raise the error to the user.
Before this change, the user would get a
JSONDecodeError
, which made no sense for them and is not pointing out the error very well, but with this the error becomes a bit better for the user to know what happened.Changes
Error Before
Error After
Tests
Known Issues
Notes
Checklist
CONTRIBUTORS.md
) in the pull request source branch.