#34632: Let makemigrations output an error message with --check
------------------------------------------------+------------------------
Reporter: ProbstDJakob | Owner: nobody
Type: Cleanup/optimization | Status: new
Component: Migrations | Version: 4.2
Severity: Normal | Keywords:
Triage Stage: Unreviewed | Has patch: 0
Needs documentation: 0 | Needs tests: 0
Patch needs improvement: 0 | Easy pickings: 0
UI/UX: 0 |
------------------------------------------------+------------------------
With the [[https://github.com/django/django/pull/15845|PR 15845]]
regarding the Issue #34051 the option `--check` does not output any errors
when changes have been detected. This seems counter intuitive for at least
unix users. Command line tools for unix typically do not output anything
if everything goes well but print an error message if something went
wrong. Furthermore if the command is run in a pipeline it is not possible
to know for certain if the command failed because of a wrongly set up
pipeline job or if a migration is actually missing. Outputting the
detected changes also leverages the person looking into the pipeline job
to know what is missing without the need to check out the changes and
actually create the migration, thus giving the person the opportunity to
make further decisions. A possible solution could be to make the flag
`--check` imply the flag `--dry-run` and move the `if check_changes:` back
down.
--
Ticket URL: <https://code.djangoproject.com/ticket/34632>
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/010701888b0cf777-ed265887-e6c5-436f-a6bb-f8a5621d6c98-000000%40eu-central-1.amazonses.com.
