fix "Unexpected fields" in parameter examples#19
Merged
kevindew merged 1 commit intokevindew:mainfrom Feb 9, 2021
Merged
Conversation
|
Same here, thanks for the quick fix, you spotted it faster than me ! |
Owner
|
Oh great - thanks for catching this. I'll get a new release made for it shortly. |
Owner
|
I've released this as part of version 0.9.0 - thanks again. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
On path parameters with
examplesthe document doesn't validate with["Unexpected fields: value"]. This is due to probably a typo inOpenapi3Parser::NodeFactory::ParameterLike#examples_factory, usingNodeFactory::Schemainstead ofNodeFactory::Example. This PR fixes that.Example from an OpenApi3 spec:
This PR fixes
Openapi3Parser.load_file('openapi.yaml').errorsresulting in["Unexpected fields: value"].