Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Naming a schema "properties" causes incorrect validation error #250

Open
ghost opened this issue Dec 4, 2019 · 0 comments
Open

Naming a schema "properties" causes incorrect validation error #250

ghost opened this issue Dec 4, 2019 · 0 comments

Comments

@ghost
Copy link

ghost commented Dec 4, 2019

If the name of a schema under the /#/components/schemas section is "properties" then we get the inaccurate warning of "Invalid definition, object type is missing" at /#/components/schemas line

components:
schemas:
properties:

I think this is bug.
@ghost ghost changed the title Invalid definition, object type is missing at /#/components/schemas line Naming a schema "properties" causes incorrect validation error Jan 23, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
0 participants