| 6 | | Ok. I was able to swap the operations when I appended a dependency on field removal of all of its bases. If you don't mind me asking, how am I able to know that is the field we are tryna remove? I am reading the code currently, but i will still leave this "dumb" question here just in case I don't find it by the time. |
| | 6 | I am not able to figure out how adjusting `check_dependency`, could help |
| | 7 | solve this issue. Assuming that I loop through all fields present in the |
| | 8 | base model, check if they're present in the inherited model, and if there |
| | 9 | are any such fields present, append `base_app_label, base_name, |
| | 10 | field_name, False` to `dependencies`, how would adjusting |
| | 11 | `check_dependency` able to reorder the migrations? |