Skip to content
This repository was archived by the owner on Sep 2, 2024. It is now read-only.

Error Responses content changed#162

Closed
RubenBG7 wants to merge 1 commit intomainfrom
RubenBG7-patch-9
Closed

Error Responses content changed#162
RubenBG7 wants to merge 1 commit intomainfrom
RubenBG7-patch-9

Conversation

@RubenBG7
Copy link
Contributor

According to Issue Aggreement

According to Issue Aggreement
@hdamker
Copy link
Contributor

hdamker commented Feb 27, 2023

If the purpose of the document is no longer that of an example (indicated by the new title and description "Common data and errors for CAMARA APIs") it should contain only componentes/schemas which are already agreed as common across the sub projects. Which is only the error info schema, but not "MoneyAmount" and others.

@shilpa-padgaonkar
Copy link
Contributor

AFAIK, it was meant to be an example. @RubenBG7 :Was this scope somehow changed ? If not, could you kindly rename the doc accordingly (for e.g. Camara_common_examples.json)?

@jpengar jpengar requested a review from PedroDiez February 28, 2023 09:11
Copy link
Contributor

@PedroDiez PedroDiez left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Some suggestions regarding HTTP "status", and "message" text

"example": {
"status": 409,
"code": "CONFLICT",
"message": "Schema validation failed at ..."
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
"message": "Schema validation failed at ..."
"message": "A specified resource duplicate entry found"

"example": {
"status": 400,
"code": "FAILED_PRECONDITION",
"message": "Schema validation failed at ..."
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
"message": "Schema validation failed at ..."
"message": "Request cannot be executed in the current system state."

"$ref": "#/components/schemas/ErrorInfo"
},
"example": {
"status": 400,
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
"status": 400,
"status": 412,

"example": {
"status": 400,
"code": "OUT_OF_RANGE",
"message": "Schema validation failed at ..."
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
"message": "Schema validation failed at ..."
"message": "Client specified an invalid range."

"$ref": "#/components/schemas/ErrorInfo"
},
"example": {
"status": 503,
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
"status": 503,
"status": 504,

"$ref": "#/components/schemas/ErrorInfo"
},
"example": {
"status": 504,
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
"status": 504,
"status": 503,

"default": "TOO_MANY_REQUESTS",
"description": "Either out of resource quota or reaching rate limiting."
}
"description": "Already Exists",
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
"description": "Already Exists",
"description": "Too Many Requests",

"name": "API DIGITAL INTEGRATION",
"email": "apidigital.integration@telefonica.com"
}
"description": "Common data and errors for CAMARA APIs",
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@RubenBG7 : Could you please change the description and title such that it clearly states that this is just a sample?

@shilpa-padgaonkar
Copy link
Contributor

@RubenBG7 : Will your new PR #176 make this one obsolete?
If yes, kindly confirm so that this PR can be closed.

@RubenBG7
Copy link
Contributor Author

Confimed @shilpa-padgaonkar PR #176 make these ones obseolete

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants