You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When I run makeviewmigration, it generates a migration file called, e.g., 0034_auto_20231130_2243.py.
I understand that that is the Django default, but it is not easy to understand. It would be much easier to read if
your migrations had names like the built in migration tools: Minimally something like 0034_person_doctor.py,
where person and doctor were names of the models that you were creating or altering views for.
Even better would be if it could do ...create_person_alter_doctor.py depending on the view existing before then.
The text was updated successfully, but these errors were encountered:
When I run
makeviewmigration
, it generates a migration file called, e.g.,0034_auto_20231130_2243.py
.I understand that that is the Django default, but it is not easy to understand. It would be much easier to read if
your migrations had names like the built in migration tools: Minimally something like
0034_person_doctor.py
,where
person
anddoctor
were names of the models that you were creating or altering views for.Even better would be if it could do
...create_person_alter_doctor.py
depending on the view existing before then.The text was updated successfully, but these errors were encountered: