#23341: Better stacktrace error for makemigrations when migration references
nonexistent migration(s)
--------------------------------------+------------------------------------
     Reporter:  rsalmaso              |                    Owner:  nobody
         Type:  Cleanup/optimization  |                   Status:  new
    Component:  Migrations            |                  Version:  1.7-rc-3
     Severity:  Normal                |               Resolution:
     Keywords:                        |             Triage Stage:  Accepted
    Has patch:  1                     |      Needs documentation:  0
  Needs tests:  1                     |  Patch needs improvement:  0
Easy pickings:  0                     |                    UI/UX:  0
--------------------------------------+------------------------------------

Comment (by rsalmaso):

 Update PR:
 - changed message from "Migration %s dependencies references nonexistent
 {parent,child} node %r" to "Migration %s dependencies references
 nonexistent {parent,child} node %r"
 - added tests for missing {parent,child} nodes

 For forwards_plan and backwards_plan I'll open a new ticket.

-- 
Ticket URL: <https://code.djangoproject.com/ticket/23341#comment:4>
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/066.09f9f21456258487b63338fc225e900c%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to