-
Notifications
You must be signed in to change notification settings - Fork 230
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
http-specs, test case on status code range #5577
base: main
Are you sure you want to change the base?
http-specs, test case on status code range #5577
Conversation
@scenarioService("/response/status-code-range") | ||
namespace Response.StatusCodeRange; |
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.
Let me know if anyone has better opinion on folder/namespace.
I thought about "payload" folder, but this is not exactly payload.
""") | ||
@route("/error-response") | ||
@get | ||
op errorResponse(): 204 | ErrorInRange | DefaultError; |
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 can remove DefaultError
, as this one would not affect the code in range (494-499).
Having it there serves another scenario that different status code result into different error model in client.
All changed packages have been documented.
|
You can try these changes here
|
Currently I only added case for the range in error response.
Range can also happen on success response (e.g. 200-299).