-
Notifications
You must be signed in to change notification settings - Fork 28
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
Normalization of error status and code allowed values #316
Normalization of error status and code allowed values #316
Conversation
Co-authored-by: Eric Murray <[email protected]>
Co-authored-by: Eric Murray <[email protected]>
…o normalize_error_status_code_enums_in_error_responses
PR ready for review (@patrice-conil, @eric-murray, @rartych, @shilpa-padgaonkar) |
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.
Just a remark about difference between 410/412 errors (see comment)
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
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
What type of PR is this?
What this PR does / why we need it:
This PR aims to define a normalization of error
status
andcode
allowed values for CAMARA APIs, by means of the use of a common chema model that can be applied for every excepction scenario.Taking advantage of this PR also a correction is managed:
422 UNSUPPORTED_DEVICE_IDENTIFIERS
exception renamed to422 UNSUPPORTED_IDENTIFIER
indicated in API Design guidelines is also included inCAMARA_common.yaml
Also making exceptions alignment as per this comment in
CAMARA_common.yaml
. Updates in API Design guidelines Section 6.2 will be managed by Update error codes and info.description template for device / phone number identifiers #324 and Enhancements and Alignments in Errors #329Which issue(s) this PR fixes:
Fixes #196
Does this PR introduce a breaking change?
Special notes for reviewers:
Documentation impacted:
Once this PR is agreed (i.e. the baseline), other artifacts would have to be updated:
We can talk this point in the next commonalities meeting (14/10) and aligned this with @bigludo7
Changelog input
Additional documentation
N/A