Uh oh!
There was an error while loading.Please reload this page.
- Notifications
You must be signed in to change notification settings - Fork2.2k
Add discriminated union related metadata entries to theCoreMetadata
definition#11216
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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
Uh oh!
There was an error while loading.Please reload this page.
Conversation
Deploying pydantic-docs with |
Latest commit: | de894e3 |
Status: | ✅ Deploy successful! |
Preview URL: | https://760627cb.pydantic-docs.pages.dev |
Branch Preview URL: | https://discriminated-union-meta-typ.pydantic-docs.pages.dev |
CodSpeed Performance ReportMerging#11216 willnot alter performanceComparing Summary
|
Coverage reportClick to see where and how coverage changed
This report was generated bypython-coverage-comment-action |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others.Learn more.
Yep, this makes sense.
I would love to not have to apply discriminators after schema build, but I don't think we know of a great way around that for now.
This is more consistent with the metadata pattern we currently use elsewhere, at least.
Would also love to have another discussion about moving thatmetadata
structure topydantic-core
so that we can avoid all of the internal casting...
9dc7d0b
intomainUh oh!
There was an error while loading.Please reload this page.
From#10655.
Change Summary
Related issue number
Checklist