#32217: Add warning about missing 'migrations' package to migration docs
-------------------------------------+-------------------------------------
Reporter: Tim McCurrach | Owner: Tim
Type: | McCurrach
Cleanup/optimization | Status: closed
Component: Documentation | Version: 3.1
Severity: Normal | Resolution: wontfix
Keywords: | Triage Stage:
| Unreviewed
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Tim McCurrach):
Fair enough. I'll concede this one haha.
Thanks both for reviewing it :)
Replying to [comment:4 Carlton Gibson]:
> Hi Tim. Thanks for the report.
>
> I have to say I agree with Mariusz. The migrations topic links directly
to the command docs, which state the behaviour quite clearly.
>
> It's stated that migrations live in the migrations directory and I don't
think labouring what happens if that's missing, or adding multiple links
to the same command docs from the same section would add clarity. Equally
I'm not sure that there's a better place for this than the
`makemigrations` command docs.
>
> Docs can always be better, so if you which to suggest changes we're
happy to review.
--
Ticket URL: <https://code.djangoproject.com/ticket/32217#comment:5>
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/071.e1a404c14c5b2c889c80e83b587cec75%40djangoproject.com.
