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
feat: Add error_details property to GoogleAPICallError based on google.rpc.status.details. #286
feat: Add error_details property to GoogleAPICallError based on google.rpc.status.details. #286
Changes from 2 commits
288019c
04b5775
5cebe8e
5b3f7c1
7b7504d
fe708ae
813fc33
d10157f
88e6ffa
b6c9e56
02b082a
12edc5a
626f7de
a844fed
a830887
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.
Is
details
property has been occupied? If not, is that better to usedetails
as name orstatus_details
relate togoogle.rpc.Status.details
.Notice that we need to keep consistency between grpc and REST.
IMO, I prefer
status_details
. WDYT @busunkim96 @tseaver @atulepThere 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 followed the naming convention in design doc. I personally prefer
details
because it's a common denominator betweengoogle/rpc/error_details.proto
andgoogle.rpc.Status.details
.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 changed the name to "details".