You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The PhantomSized type is "too" flexible. Consider adding an intermediary BoundedSize or similar that takes class arguments min/max and reflects that in minItems/maxItems.
The text was updated successfully, but these errors were encountered:
Not sure if I'm running in to the mentioned Caveat regarding pydantic and NonEmpty below? Or is it a separate issue I'm running in to? (Feels a little bit like I'm running in to some problem with sub-field type not being available)
Currently there are two issues:
Pydantic doesn't expose the "sub-field" type toFixed in Add optional__modify_schema__
so we can't add e.g.{items: {"type": "integer"}}
for aNonEmpty[int]
. See discussion.field
argument to__modify_schema__
pydantic/pydantic#3434.PhantomSized
type is "too" flexible. Consider adding an intermediaryBoundedSize
or similar that takes class argumentsmin
/max
and reflects that inminItems
/maxItems
.The text was updated successfully, but these errors were encountered: