Closed jlurien closed 1 year ago
Suppose this issue is done:
- Most of changes apply to current property names, as they must be formattted in snake_case. This can be addressed together with issue #90 in a new PR, when new terms are agreed.
The final decision in Commonalities was camelCase for property names, which we will continue to use. Also the new terms are applied (with #129)
- We have to adapt errors, adding
status
, and at a same time we could enhance current documentation and examples. This can be done in separate PR.
Done with #104
All done.
Some weeks ago, a set of API design guidelines have been approved in commonalities.
Regarding terminolgy and style:
Errors must include:
status
, which can be identified in the response as a standard code from list of Hypertext Transfer Protocol (HTTP) response status codes.code
, which can be identified and traced for more details. It must be human readable; therefore, it must not be a numeric code. In turn, to achieve a better location of the error, you can reference the value or field that is causing it, and include it in the message.message
.Proposed actions
Most of changes apply to current property names, as they must be formattted in snake_case. This can be addressed together with issue #90 in a new PR, when new terms are agreed.
We have to adapt errors, adding
status
, and at a same time we could enhance current documentation and examples. This can be done in separate PR.