We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Example Swagger/OpenAPI definition:
{ "openapi": "3.1.0", "info": { "title": "Server", "version": "0.0.1" }, "paths": { "/endpoint": { "get": { "responses": {}, "parameters": [ { "name": "param", "in": "query", "content": { "application/json": { "schema": { "type": "array", "items": { "type": "object", "properties": { "a": { "type": "string" }, "b": { "type": "number" } } } } } } }, { "name": "secondParam", "in": "query", "content": { "application/json": { "schema": { "type": "object", "properties": { "a": { "type": "object", "properties": { "a": { "type": "object", "properties": { "a": { "type": "string" }, "b": { "type": "number" } } }, "b": { "type": "number" } } }, "b": { "type": "number" } } } } } } ] } } } }
Errors for nested parameters aren't properly formatted and sometimes show undefined string.
undefined
Errors should be formatted in a clear way, ex. a.b.c: value must be a string or a[b][c]: value must be a string or a: b: c: value must be a string
a.b.c: value must be a string
a[b][c]: value must be a string
a: b: c: value must be a string
They should also not contain the undefined string, instead it should be shown without trying to specify the affected value, ex:
This is a follow up for #9687. The validationErrors function should be updated to take nested parameters/errors into account.
validationErrors
The text was updated successfully, but these errors were encountered:
fix(spec): format validation errors for nested parameters
2dcc387
Refs #9774
fix(spec): format validation errors for nested parameters (#9775)
0f395c2
Addressed in 0f395c2
Sorry, something went wrong.
glowcloud
No branches or pull requests
Q&A (please complete the following information)
Content & configuration
Example Swagger/OpenAPI definition:
Describe the bug you're encountering
Errors for nested parameters aren't properly formatted and sometimes show
undefined
string.Expected behavior
Errors should be formatted in a clear way, ex.
a.b.c: value must be a string
ora[b][c]: value must be a string
ora: b: c: value must be a string
They should also not contain the
undefined
string, instead it should be shown without trying to specify the affected value, ex:Additional context or thoughts
This is a follow up for #9687. The
validationErrors
function should be updated to take nested parameters/errors into account.The text was updated successfully, but these errors were encountered: