#31468: Move migration name suggestion from AutoDetector to operation classes
-------------------------------------+-------------------------------------
Reporter: Adam | Owner: nobody
(Chainz) Johnson |
Type: New | Status: assigned
feature |
Component: | Version: master
Migrations |
Severity: Normal | Keywords:
Triage Stage: | Has patch: 1
Unreviewed |
Needs documentation: 0 | Needs tests: 0
Patch needs improvement: 0 | Easy pickings: 0
UI/UX: 0 |
-------------------------------------+-------------------------------------
Currently migration automatic names are generated in one method in the
autodetector. This does not support all operation types, and has no way of
being extended for custom operation types. This logic should be moved to
the individual operations classes.
--
Ticket URL: <https://code.djangoproject.com/ticket/31468>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/053.855bd25f00cd822f8e4e8aa6726c8473%40djangoproject.com.
