Support inline oneOf discriminated properties #27
Conversation
This file contains 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.
Pydantic exported schemas do not commonly support
allOfinheritance (see pydantic/pydantic#478) and regularly emit inline property schemas comprised of adiscriminatorwith custom mappings and aoneOfconstraint.Following support for
oneOfintroduced in #23 this PR extends this support to inline discriminated schema properties by converting the original schema into an inheritance tree usingallOf.The main current limitation is for definitions participating in multiple distinct discriminated unions: in this case the first discriminator will be used as the root of the inheritance and no multiple inheritance is allowed.
Fixes #25