Improve runserver migration notification output.

[Keryn Knight]

Firstly, it uses the word "app" when it's actually over the whole project, and may span multiple apps, to use the Django nomenclature.

Additionally, I think it would be nicer to know what might need applying. At the very least, the number should be easy enough to ascertain (len(plan) I'd assume), changing the message to something like:

You have 3 unapplied migrations; your project may not work correctly until apps [auth, bob, myapp] have their migrations applied.

would overall be preferable; the names can I think be gained via sorted(set(x[0].app_label for x in plan))

Could be easy pickings if accepted.

[Claude Paroz]

More accurate messages (when possible) are always welcome.

[Emre Yılmaz]

Related pull request is on github:
​https://github.com/django/django/pull/5765

[Emre Yılmaz]

Patch for ticket #25855

[Claude Paroz]

To be seen if tests are doable in this part of the code.

[Emre Yılmaz]

Couldn't find a good way to test this with the current test structure. Any starting point?

[Claude Paroz]

It might be possible to instanciate a runserver Command and to call check_migrations without running the command itself.

[Emre Yılmaz]

Just added the related unit tests and updated the pull request on github:

​https://github.com/django/django/pull/5765

[Tim Graham]

Don't forget to uncheck the appropriate ticket flags after updating a patch ("Needs tests" in this case). Also, you don't need to add a patch on the ticket when you also send a pull request. Thanks!

[Emre Yılmaz]

Sorry, trac is a new thing for me :-)

thanks for the heads up.

[Tim Graham <timograham@…>]

In 63a6a653:

Fixed #25855 -- Enhanced the migration warning for runserver.

Added unapplied migration count and the list of unmigrated apps.