Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Improve default migration naming #27

Open
ckoppelman opened this issue Dec 26, 2023 · 1 comment
Open

Improve default migration naming #27

ckoppelman opened this issue Dec 26, 2023 · 1 comment
Labels
enhancement New feature or request

Comments

@ckoppelman
Copy link

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.

@BezBartek BezBartek added the enhancement New feature or request label Dec 26, 2023
@BezBartek
Copy link
Owner

BezBartek commented Dec 26, 2023

Hello, thank you for comment, I 100% agree with your idea, to improve migration naming.
This shouldn't be hard to add
I will add it

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants