#24899: Split up migrations autodetector._detect_changes into separate functions
-------------------------------------+-------------------------------------
Reporter: MarkusH | Owner: nobody
Type: | Status: new
Cleanup/optimization |
Component: | Version: master
Migrations |
Severity: Normal | Keywords: afraid-to-commit
Triage Stage: | Has patch: 0
Unreviewed |
Needs documentation: 0 | Needs tests: 0
Patch needs improvement: 0 | Easy pickings: 1
UI/UX: 0 |
-------------------------------------+-------------------------------------
The migration autodetector is one important part of Django's migration
framework. The "magic" happens in its method `_detect_changes()` which
spans more than 200 lines of code. Although the method already has some
structure, it would be great to move the different steps that are
performed in there into separate methods.
--
Ticket URL: <https://code.djangoproject.com/ticket/24899>
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 post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/050.7319199d87089ad4ca30c5f4dcf9a849%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
