-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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
oneOf nested in an allOf prevents allOf from displaying all in v2.0.0-alpha.38 #641
Comments
Behavior confirmed in v2.0.0-alpha.39 as well. |
Behavior confirmed in v2.0.0-alpha.40. |
@trip-somers Thanks for verifying. I will look into this a bit later. Sorry for the delay. |
Just a note for myself Got able to minify the reproducible sample down to: Main:
title: Sale
description: A request to authorize and capture funds.
allOf:
- $ref: '#/components/schemas/SchemaWithOneOfWithRefInside'
- type: object
properties:
b:
type: number
SchemaWithOneOfWithRefInside:
oneOf:
- $ref: "#/components/schemas/Anything"
Anything:
type: object
properties:
a:
type: string Looks like |
Also seems to happen with anyOf nested inside a allOf (2.0.0 rc0) |
Well, this pretty annoying issue preventing using the full power of the polymorphism in OpenAPI. |
Before (v2.0.0-alpha.37):
After (v2.0.0-alpha.38 -- missing Body.Order.Transaction):
YAML:
I looked over a diff on .38 vs .37, and I did not immediately see a cause for this. I can provide more detail if necessary.
The text was updated successfully, but these errors were encountered: