#26292: Refactor MigrationLoader.build_graph() to use more of MigrationGraph's
features
------------------------------------------------+-------------------------
Reporter: MarkusH | Owner: jarekwg
Type: Cleanup/optimization | Status: new
Component: Migrations | Version: master
Severity: Normal | Keywords:
Triage Stage: Accepted | Has patch: 0
Needs documentation: 0 | Needs tests: 0
Patch needs improvement: 0 | Easy pickings: 0
UI/UX: 0 |
------------------------------------------------+-------------------------
The `build_graph` method on the `MigrationWriter` is rather complex and
hard to understand. While talking to @jarekwg about #25945 we came to the
conclusion that it would be worth to see if moving parts of that method
into the `MigrationGraph` would be suitable.
General idea:
1. Add all normal migrations
1. Add all their dependencies (create dummy nodes for non-existing
squashed migrations)
1. Replace the nodes in the graph when they have been replaces with
suitable squashed migrations and update the dependencies accordingly
1. Ensure there are no dummy nodes left in the graph and the graph is
consistent.
--
Ticket URL: <https://code.djangoproject.com/ticket/26292>
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 django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/050.7c0077a4a019e40ee317a62df7fb4e10%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
