Support baking different scenarios of oneOf usage in openapi spec #773
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.
📝 Description
Previously, the schema expected oneOf to be defined strictly within the properties block of the YAML file, limiting flexibility in structuring the schema. This update allows oneOf to be defined outside of properties in yaml files, e.g. schema definitions like below:
✔️ How to Test
Download
openapi.json
file from Akamai git source v4.199.0SPEC=/path/to/openapi.json make test-int
📷 Preview
If applicable, include a screenshot or code snippet of this change. Otherwise, please remove this section.