Migrations won't work if field signature changes
|Reported by:||Markus Holtermann||Owned by:||rjasjukaitis|
|Cc:||info@…, rjasjukaitis||Triage Stage:||Accepted|
|Has patch:||no||Needs documentation:||no|
|Needs tests:||no||Patch needs improvement:||no|
__init__ signature of a model field changes in the way that e.g. a positional argument is added / removed and doesn't replace / isn't replaced by a previously existing keyword argument, the old migration files won't work any more because the rely on the actual
__init__ signature to create an instance of the field.
This should be documented in the respective custom field and migration docs.