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
@DrJfrost ninja-schema compiles to django model fields to pydantic fields with validations based on the field in question.
For example, an email field won't result to just a string type pydantic field but also a string type with email validation
wouldn't it be better to extend the ninja's buitlin modelschema? from a large project perspective having to install 3 extra packages just to set up a rest api seems a bit too much. or at least make it part of the ninja-extra setup. if the project is oriented to be django friendly it should then inherently include all the tools in it. just like DRF does with views viewset's modelviewset etc
@DrJfrost I think it's a good idea to move it into the django-ninja extra.
Thanks for the suggestions. It will be done in future releases of django-ninja extra
As the title says I find a little redundant to recreate the
modelchema
https://django-ninja.dev/guides/response/django-pydantic/ shouldn't the original django-ninja
modelschema
be used?The text was updated successfully, but these errors were encountered: