Skip to content
This repository has been archived by the owner on Jan 25, 2023. It is now read-only.

varianttype and alternateBases should use oneof construct in OpenAPI specs #273

Open
blankdots opened this issue Feb 21, 2019 · 0 comments
Milestone

Comments

@blankdots
Copy link

This has been identified in #252 but here it is as a separate issue.

I think https://swagger.io/docs/specification/data-models/oneof-anyof-allof-not/#oneof should be used for alternateBases and variantType see lines:

It is my understanding both cannot be used in queries, it should be only one of them.

@blankdots blankdots changed the title varianttype and alternateBases should use oneof construt in OpenAPI specs varianttype and alternateBases should use oneof construct in OpenAPI specs Feb 21, 2019
@sdelatorrep sdelatorrep added this to the spec 1.2 milestone Mar 22, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants