Model validation should complain if both `add_now` and `auto_add_now` are specified.
|Reported by:||Simon Charette||Owned by:||anonymous|
|Component:||Database layer (models, ORM)||Version:||master|
|Has patch:||yes||Needs documentation:||no|
|Needs tests:||no||Patch needs improvement:||yes|
It was reported in #21785 that
auto_add_now can be both specified without triggering any kind of warning or validation or value error.
Not sure of the path we want to take here since it should be pretty uncommon and easily fixed by the users. Would an accelerated deprecation be acceptable?
In order to ease the merge of the
check framework before the 1.7 alpha we should wait before landing a fix.
Change History (18)
comment:3 Changed 3 years ago by
|Owner:||changed from Simon Charette to anonymous|
|Status:||new → assigned|
comment:16 Changed 2 years ago by
|Patch needs improvement:||set|