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
Hello, I'm thinking to enable the aliases on the fields. It would enable a cleaner attribute validation to avoid conflicts between builtin methods and the fields for example (as already done by Pydantic).
The current behavior I'm thinking of:
If a field has an alias and no key_name, the resulting document key will be the alias
It's still possible to customize the key_name with an alias already set by specifying the key_name kwarg
Do you think some more customization/options would be useful ?
The text was updated successfully, but these errors were encountered:
An object creation are possible from dict with alias/field keys, but document creation itself should be regulated using parameter like by_alias , that pydantic's dict method already have.
Hello, I'm thinking to enable the aliases on the fields. It would enable a cleaner attribute validation to avoid conflicts between builtin methods and the fields for example (as already done by Pydantic).
The current behavior I'm thinking of:
alias
and nokey_name
, the resulting document key will be the aliaskey_name
kwargDo you think some more customization/options would be useful ?
The text was updated successfully, but these errors were encountered: