add parsing error detail to ParseError when parsing response fails #659
Conversation
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
supermihi
force-pushed
the
add-parseerror-detail
branch
from
b0c5e1b to
8ed27da
Compare
dbanty
approved these changes
Aug 27, 2022
Codecov Report
@@ Coverage Diff @@
## main #659 +/- ##
=========================================
Coverage 100.00% 100.00%
=========================================
Files 49 49
Lines 1794 1795 +1
=========================================
+ Hits 1794 1795 +1
📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more |
|
Welcome, thanks for merging! :-) |
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.
Without this change, it is very hard for users to trace what actually caused the parsing error.