Allow to know whether a field is required about tortoise-orm HOT 3 CLOSED

Yes, I think we can safely auto-generate the "required" attribute from a combination of the null and default parameters.

In Django the "blank" parameter is only really used by auto-form generation and is otherwise ignored. It is one of the areas where persistence rules and presentation rules is mixed, which is not ideal, as it implies inter-dependency. So lets see if we can leave it out.

Also, have a look at #13 & #39 which is both features we wanted to get to post 1.0, but as you are showing interest :-)

Also #14 which led to a more standardised init, it also makes models cleaner to discover. So If there is anything you feel is needed, we could extend that interface to provide.
I'd prefer something explicit, and not an implementation detail, so we have the capability of changing internals without breaking it for everyone.

from tortoise-orm.

In Django the "blank" parameter is only really used by auto-form generation and is otherwise ignored.

FYI, I believe the Django REST Framework does use blank to figure out whether a field is required (which makes sense because a REST POST request is a form too, in a way).

But it always seemed strange to me that we needed to specify blank=True even though a default was passed, hence the proposal which we seem to agree upon. :-)

I'd prefer something explicit, and not an implementation detail, so we have the capability of changing internals without breaking it for everyone.

I'm not sure what you mean exactly by this?

Also, I've taken a look at those issues you mentioned and will keep them under my radar. :-)

from tortoise-orm.

I meant that we should instead of letting the user use what is currently an internal interface, instead formalise it, so that we can at worst know exactly what we need to keep compatible for, in case of internal change.

E.g. we need to support deprecation period, so if we need to change something incompatibily internally, we can still have a stable interface for this, so that we annoy our users less.
A good read on this topic (and many others) is: https://emptysqua.re/blog/api-evolution-the-right-way/

from tortoise-orm.