[Spec] add petstore-3.0-native.yaml spec with oneOf
request schema
#511
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.
PR checklist
./bin/
to update Petstore sample so that CIs can verify the change. (For instance, only need to run./bin/{LANG}-petstore.sh
and./bin/security/{LANG}-petstore.sh
if updating the {LANG} (e.g. php, ruby, python, etc) code generator or {LANG} client's mustache templates). Windows batch files can be found in.\bin\windows\
.master
,3.1.x
,4.0.x
. Default:master
.Description of the PR
As more specs start to use OpenAPI 3.0 native features, it is becoming more important to test them.
This PR adds a
petstore-3.0-native.yaml
spec to contain native OpenAPI 3.0 spec artifacts, likeoneOf
, as opposed to be converted from a 2.0 spec. This is based onresources/3_0/petstore.yaml
and currently contains the additionalPATCH /pets
endpoint as seen below. More will be added to this spec so we can have a test spec as we build out OAS3 features.https://swagger.io/docs/specification/data-models/oneof-anyof-allof-not/
This has been validated here:
https://mermade.org.uk/openapi-converter