Model validation should complain if both `add_now` and `auto_add_now` are specified.
|Reported by:||charettes||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 add_now and 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 16 months ago by PirosB3
- Owner changed from charettes to anonymous
- Status changed from new to assigned
comment:8 Changed 16 months ago by charettes
comment:16 Changed 15 months ago by timo
- Easy pickings unset
- Needs documentation unset
- Needs tests unset
- Patch needs improvement set
comment:17 Changed 14 months ago by Tim Graham <timograham@…>
- Resolution set to fixed
- Status changed from assigned to closed