Changing a m2m through= from one custom model to another is no-op'd instead of raising an error
Bug in b25aee3b7bef07dd07bed2209efcdf1a8146112c of ticket #22476.
The check to make changes to field options like blank=True on m2m's with a custom through model no-ops is currently only checking that both through models were non-auto-created source, rather than verifying they are the same model. This means any two custom through models would satisfy the check and short-circuit.
See regression test in PR for how to reproduce.
Change History
(6)
| Description: |
modified (diff)
|
| Triage Stage: |
Unreviewed → Accepted
|
| Patch needs improvement: |
set
|
| Patch needs improvement: |
unset
|
| Triage Stage: |
Accepted → Ready for checkin
|
| Patch needs improvement: |
set
|
| Triage Stage: |
Ready for checkin → Accepted
|
Thank you Clifford! Well spotted!