| 17 | | It seems to me that there is probably something that reorders the order of the action operations before it prints out action operations executed in the console. In this case, it should've been `["RemoveField", "RemoveField", "CreateModel", "CreateModel"]`, but currently it is `["CreateModel", "CreateModel", "RemoveField", "RemoveField"]`. But the program is still able to solve the issue when `makemigrations`. How am i supposed to write test cases for that? |
| 18 | | |
| 19 | | [https://github.com/django/django/blob/master/django/core/management/commands/makemigrations.py#L164-L169] in `makemigrations.py` makes the order correct. But i guess the order isn't adjusted before this. |
| | 17 | In this case, it should've been `["RemoveField", "RemoveField", "CreateModel", "CreateModel"]`, but currently it is `["CreateModel", "CreateModel", "RemoveField", "RemoveField"]`. But the program is still able to solve the issue when `makemigrations`. How can I create one migration for `Readable` first and then create the second one for the updated models? |