| 18 | | Fully support listing the dependency both ways, as `0001_initial_squashed_0002_blah` and as `0002_blah`. For cases where the migration tree is in the unsquashed reality and thus does not contain `0001_initial_squashed_0002_blah`, have it inspect the 'replaces' list in `0001_initial_squashed_0002_blah.py`, pick out the most recent migration (ie `0002_blah`) and use that instead. |
| 19 | | |
| 20 | | Another (perhaps cleaner, yet less clear) solution: |
| 21 | | |
| 22 | | Have `makemigrations` not point newly created migrations at squashed migrations, but rather at the squashed migrations' last dependency. This would solve the issue with `makemigrations` automatically creating problematic migrations. It would be cleaner as there'd only be one ''correct'' migration to point to, however it could result in confusion for people manually creating their migrations and pointing them at the wrong thing. |
| | 18 | Fully support listing the dependency both ways, as `0001_initial_squashed_0002_blah` and as `0002_blah`, using fancy logic to ensure valid references to inapplicable migrations are appropriately rerouted. |