-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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
Online editor reports several nonsensical errors #1519
Comments
Nevermind. I found out what breaks it. It is that I was using a openapi: 3.0.0
info:
title: Example API
description: Service API.
version: 1.0.0
servers:
- url: 'http://api.example.com'
paths:
/login/local:
post:
tags:
- login
summary: Login using email or nickname
description: Returns customer info and jwt access and refresh tokens
security:
- apiKey: []
requestBody:
content:
application/json:
schema:
type: object
required:
- emailOrNickname
- password
properties:
emailOrNickname:
type: string
password:
type: string
responses:
'200':
description: Login successful
content:
application/json:
schema:
type: object
properties:
customer:
$ref: "#/components/schemas/Admin"
refreshToken:
type: string
"401":
description: "Unauthorized"
components:
securitySchemes:
apiKey:
type: apiKey
in: header
name: x-application-key
schemas:
Admin:
type: object
properties:
_id:
type: string
name:
type: object
properties:
first:
type: string
last:
type: string
email:
type: object
properties:
address:
type: string
verified:
type: boolean
token:
type: string
password:
type: string
recoveryToken:
type: string
lastLogin:
type: string
format: date-time |
Thanks for reporting the issue and the fix. I'm going to reopen the ticket since we need to rework that validation message. It's not useful to users and we should do a better job at it. |
Similar nonsensical error when using openapi: "3.0.0"
info:
version: 1.0.0
title: A thing
license:
name: AGPL-3.0
paths:
/excellence:
get:
responses:
'200':
description: "An excellent response"
content:
application/json:
schema:
type: array
items:
$ref: "#/components/schemas/ExcellentThing"
components:
schemas:
ExcellentThing:
description: "Something excellent"
properties:
extremelyExcellent:
description: "If false, this item is only somewhat excellent"
type: bool
example: true Errors: Above schema with actual problem fixed: ( openapi: "3.0.0"
info:
version: 1.0.0
title: A thing
license:
name: AGPL-3.0
paths:
/excellence:
get:
responses:
'200':
description: "An excellent response"
content:
application/json:
schema:
type: array
items:
$ref: "#/components/schemas/ExcellentThing"
components:
schemas:
ExcellentThing:
description: "Something excellent"
properties:
extremelyExcellent:
description: "If false, this item is only somewhat excellent"
type: boolean
example: true |
I've opened a pull request (#1985) that will close this issue. Here's what Swagger Editor reports with my changes:
PS: @AlbinoDrought, the messaging for your example has been improved as well:
|
* adopt @webron's OpenAPI 3.0 schema from OAI/OpenAPI-Specification#1270 permalink: https://github.com/OAI/OpenAPI-Specification/blob/92e15eba1d4591ebfe8c11898c48241e72854381/schemas/v3.0/schema.yaml * add ajv-errors * address error messages for #1808's Swagger 2.0 example clarifies the schema and adds custom error messages for unclear error conditions * address error messages for #1808's OpenAPI 3.0 example * restrict underlying JSON Schema `type` field to simple types only (for #1832) * fix limitation in JSON Pointer conversion helper * add clear `not` error message (for #1489) * add additionalProperties message (for #1394) * add ajv-keywords * use `switch` to intelligently identify inline vs referenced content (for #1853) * use `switch` to XOR `schema` and `content` (for #1853) * use `switch` to pivot security scheme based on type (for #1672) * use switch to fall-through to inline security scheme validation (for #1672) * rewrite more Reference oneOfs (for #1519) * add custom message for `Schema.required` type error (for #1519) * rewrite Response/Reference oneOf (for #1489) * use switch in ParameterLocation validation (for #1797) * define pivot key switches for SecurityDefinitions (for #1711) * give helpful `format: uri` messages for SecurityDefinitions (for #1711) * eliminate NonBodyParameter; pivot on `Parameter.in` with a switch (for #1511) * oneOf -> switch for Parameters.items reference * (for #1711) * remove redundant semantic validator (for #1511) * adjust wording of custom error message (for #1853) * add regression tests for all related issues * revert to expect@^1.20.2 * linter fixes * fix messaging flaw for #1832 * improve messaging for #1394 * use literal key for `$ref` in Reference Object * remove commented legacy data from OAS3 schema * remove superfluous quotation marks * normalize test case paths to `/` * normalize openapi fields to 3.0.0 * drop unused `paths` information * ensure clear errors for 3.0 Parameter style/content exclusivity * add `required` assertions to switch statements that pivot on a key's value this prevents false positives when the pivot key is missing entirely * remove stray space
…i#1985) * adopt @webron's OpenAPI 3.0 schema from OAI/OpenAPI-Specification#1270 permalink: https://github.com/OAI/OpenAPI-Specification/blob/92e15eba1d4591ebfe8c11898c48241e72854381/schemas/v3.0/schema.yaml * add ajv-errors * address error messages for swagger-api#1808's Swagger 2.0 example clarifies the schema and adds custom error messages for unclear error conditions * address error messages for swagger-api#1808's OpenAPI 3.0 example * restrict underlying JSON Schema `type` field to simple types only (for swagger-api#1832) * fix limitation in JSON Pointer conversion helper * add clear `not` error message (for swagger-api#1489) * add additionalProperties message (for swagger-api#1394) * add ajv-keywords * use `switch` to intelligently identify inline vs referenced content (for swagger-api#1853) * use `switch` to XOR `schema` and `content` (for swagger-api#1853) * use `switch` to pivot security scheme based on type (for swagger-api#1672) * use switch to fall-through to inline security scheme validation (for swagger-api#1672) * rewrite more Reference oneOfs (for swagger-api#1519) * add custom message for `Schema.required` type error (for swagger-api#1519) * rewrite Response/Reference oneOf (for swagger-api#1489) * use switch in ParameterLocation validation (for swagger-api#1797) * define pivot key switches for SecurityDefinitions (for swagger-api#1711) * give helpful `format: uri` messages for SecurityDefinitions (for swagger-api#1711) * eliminate NonBodyParameter; pivot on `Parameter.in` with a switch (for swagger-api#1511) * oneOf -> switch for Parameters.items reference * (for swagger-api#1711) * remove redundant semantic validator (for swagger-api#1511) * adjust wording of custom error message (for swagger-api#1853) * add regression tests for all related issues * revert to expect@^1.20.2 * linter fixes * fix messaging flaw for swagger-api#1832 * improve messaging for swagger-api#1394 * use literal key for `$ref` in Reference Object * remove commented legacy data from OAS3 schema * remove superfluous quotation marks * normalize test case paths to `/` * normalize openapi fields to 3.0.0 * drop unused `paths` information * ensure clear errors for 3.0 Parameter style/content exclusivity * add `required` assertions to switch statements that pivot on a key's value this prevents false positives when the pivot key is missing entirely * remove stray space
@maheshJosephSadashiv this issue has been closed for over 9 months, please open a new one if you need help! |
Bug
Demonstration API definition
Configuration (browser query string, constructor, config.yaml)
I'm using the default config
Expected Behavior
I think my path definition is correct. I've read and re-read the 3.0 spec several times, I based my code on the examples on spec but I still get several weird errors: Mainly I don't want to use a component
$ref
on therequestBody
. I've seen example code on the spec documentation and it looks like I should have that optionCurrent Behavior
Context
I'm trying to migrate some bad documentation to something better using swagger 3
The text was updated successfully, but these errors were encountered: