Skip to content

Latest commit

 

History

History
33 lines (26 loc) · 1.48 KB

makemigrations.md

File metadata and controls

33 lines (26 loc) · 1.48 KB
Raw

makemigrations

The linter can override the behaviour of the Django makemigrations command.

Either:

  • by specifying the --lint option in the command line
  • by setting the MIGRATION_LINTER_OVERRIDE_MAKEMIGRATIONS Django setting to True

Example

$ python manage.py makemigrations --lint

Migrations for 'app_correct':
  tests/test_project/app_correct/migrations/0003_a_column.py
    - Add field column to a
Linting for 'app_correct':
(app_correct, 0003_a_column)... ERR
        NOT NULL constraint on columns

The migration linter detected that this migration is not backward compatible.
- If you keep the migration, you will want to fix the issue or ignore the migration.
- By default, the newly created migration file will be deleted.
Do you want to keep the migration? [y/N] n
Deleted tests/test_project/app_correct/migrations/0003_a_column.py

Options

Among the options that can be given, additionally to the default makemigrations options, you can count the options to configure what should be linted:

  • --database DATABASE - specify the database for which to generate the SQL. Defaults to default.
  • --warnings-as-errors [MIGRATION_TEST_CASE ...] - handle warnings as errors. Optionally specify the selected tests using their code.
  • --exclude-migration-tests MIGRATION_TEST_CODE [...] - specify backward incompatible migration tests to be ignored using the code (e.g. ALTER_COLUMN).