-
Notifications
You must be signed in to change notification settings - Fork 17
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
Include error ID in the error response for new error format #1454
Conversation
… Operation Attempt work
be1bb8a
to
adc748c
Compare
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.
LGTM
@@ -61,6 +61,7 @@ public CommandResult.Error apply(APIException apiException) { | |||
errorFields.put(ErrorObjectV2Constants.Fields.FAMILY, apiException.family.name()); | |||
errorFields.put(ErrorObjectV2Constants.Fields.SCOPE, apiException.scope); | |||
errorFields.put(ErrorObjectV2Constants.Fields.TITLE, apiException.title); | |||
errorFields.put(ErrorObjectV2Constants.Fields.ID, apiException.errorId); |
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.
java doc to describe what these fields are.
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.
there is a whole bunch of docs on the ApiException that explains all the fields, your comment has reminded me that it's about time we refactor the CommandResult.Error it is a mess with the map.
if we do this, then we dont need all these fields and maps etc see #1462
This was already happening for the old errors mapped to new, the new OperationAttempt work relies on this
What this PR does:
Which issue(s) this PR fixes:
Fixes #
Checklist