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.

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

Better error reporting on unsupported keywords #51

Open
fredbi opened this issue Jan 2, 2018 · 0 comments
Open

Better error reporting on unsupported keywords #51

fredbi opened this issue Jan 2, 2018 · 0 comments

Comments

@fredbi
Copy link
Member

fredbi commented Jan 2, 2018

Unsupported json keywords in swagger are a common failure for my specs which are largely inherited from previously designed json schemas.

Currently, error reporting is terse on this kind of problem.

At best, I have a "forbidden property xxx" message.
At worse, I have a "xxx does not validate oneOf ..." message.

The switch between these 2 types of message is dificult to control (related to MatchCount, which makes a best effort to provide correct reporting on anyOf|oneOf failures).

I think an additional scan with a list of json keywords explicitly not supported by swagger (e.g: $schema, additionalItems, ...) would provide the user a clearer view on what's wrong with the spec.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant