Passing schema_extra to Field has changed in Pydantic 2.0 but not in SQLModel.

[HarshTrivedi]

First Check

• I added a very descriptive title here.
• I used the GitHub search to find a similar question and didn't find it.
• I searched the SQLModel documentation, with the integrated search.
• I already searched in Google "How to X in SQLModel" and didn't find any information.
• I already read and followed all the tutorial in the docs and didn't find an answer.
• I already checked if it is not related to SQLModel but to Pydantic.
• I already checked if it is not related to SQLModel but to SQLAlchemy.

Commit to Help

• I commit to help with one of those options 👆

Example Code

No code to show. See the description.

Description

PydanticV1's Field class supported passing arbitrary keyword arguments to the JSON schema. In SQLModel counterpart, it was supported by passing schema_extra (see this).

PydanticV2 still supports passing extra things to the JSON schema but in a slightly different way. One has to pass a dictionary in the json_schema_extra argument (see this).

Currently, SQLModel does not reflect the corresponding change in its Field implementation. From what I can tell, it's simply about making one line change to the call here (call to Pydantic's FieldInfo).

# from:
**current_schema_extra,
# to:
json_schema_extra=current_schema_extra,

For consistency with Pydantic, it may also be better to rename schema_extra to json_schema_extra.

Operating System

macOS

Operating System Details

No response

SQLModel Version

0.0.16

Python Version

3.11.0

Additional Context

No response

[HarshTrivedi]

Okay, it's been over a week and I am fairly positive this is a bug. So tagging @tiangolo, @maru0123-2004 @daniil-berg, @raphaelgibson based on who have made commits to the lines surrounding the bug. I'll appreciate the help, thank you!

[HarshTrivedi]

@tiangolo Gentle reminder here.

[chenkovsky]

there's a workaround

schema_extra={
        "json_schema_extra": {
            "x-yy-zz": "zz"
        }
    }