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.
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Feature: option to retrieve original json body if parse exception occurred #886
Feature: option to retrieve original json body if parse exception occurred #886
Changes from all commits
51976d1
35c07e9
9835bc4
0e93afd
d003cc6
5bcf666
9832695
890a76b
cdeb192
e7eee8a
30ee626
435d2ef
0beeebb
d93cd29
d416490
a7b422e
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We should keep the existing constructor without the additional parameter to avoid a breaking change (and default the additional parameter to
false
).Also, to be future proof if we add more options in the features, what about changing this constructor to
RestClientOptions(RequestOptions.Builder builder)
so that we can add more properties without impacting the constructor's signature?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think the future proof constructor will make more sense when we'll have control over RequestOptions in the low level client!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why is it empty? It should set a boolean flag in the builder, and
setRetrieveOriginalJsonResponseOnException
onRestClientOptions
should be removed to keep it immutable.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
it cannot set a boolean flag in the builder, because the builder is in the RestClient code