We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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 our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
I suggest to support pydantic.Field.alias field. Currently erdantic ignores it.
pydantic.Field.alias
That's an example with simple Gift class:
Gift
from pydantic import BaseModel, Field class Gift(BaseModel): for_: str = Field(alias="for")
erdantic produces:
Although, pydantic displays a field as for:
for
>>> Gift.schema() {'title': 'Gift', 'type': 'object', 'properties': {'for': {'title': 'For', 'type': 'string'}}, 'required': ['for']}
Libraries like FastAPI use that schema in Swagger generations.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
I suggest to support
pydantic.Field.alias
field. Currently erdantic ignores it.That's an example with simple
Gift
class:erdantic produces:
Although, pydantic displays a field as
for
:Libraries like FastAPI use that schema in Swagger generations.
The text was updated successfully, but these errors were encountered: