Migration linting cannot be controlled exclusively through configuration files

The usage docs says that all of the parameters can be controlled with a configuration file (pyproject.toml or .django_migration_linter.cfg) but this is not quite true. There are a handful of configs that can only be used via arguments on the command line:

• project_root_path
• verbosity
• app_label
• migration_name
• git_commit_id
• include_migrations_from

All of these properties make explicit references to options passed to the management command rather than to config which is read from config files. Example:

https://github.com/3YOURMIND/django-migration-linter/blob/8cf37cd0f2bcd09485d698f9c573f19acbb946cf/django_migration_linter/management/commands/lintmigrations.py#L208-L213

[David-Wobrock]

Okay, thanks you two for the complimentary info 👍 While I don’t necessarily agree on all points made, I think it’s easiest and most flexible to simply allow all options to be specified in the config files too. I opened a new PR with the necessary changes https://github.com/3YOURMIND/django-migration-linter/pull/191

@phillipuniverse Interesting remark about the project_root_path as a Python settings. For now, the linter only supports one settings (MIGRATION_LINTER_OVERRIDE_MAKEMIGRATIONS), but one could imagine handling also all options as Python settings if that makes sense. In a simple pattern like f"MIGRATION_LINTER_{option_key.upper()}" or f"MIGRATION_LINTER_{option_key.upper()}_OPTION". Can I let you open another issue for this specific discussion? 😃

[phillipuniverse]

@David-Wobrock I submitted a new issue at https://github.com/3YOURMIND/django-migration-linter/issues/198