You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Thanks for creating and maintaining this. It looks useful 👍
I'm in the process of getting the linter set up for my project and have run into two small issues:
The django.contrib.gis.db.backends.postgis backend is not recognized. I think this could be mapped to postgresql safely, but I can't say for sure.
According to the docs you can specify the sql_analyser, but this isn't recognized when running the linter using makemigrations.
For the second issue, this is how config values are loaded and propagated when calling the linter management command. The same thing is unfortunately not done in the makemigrations management command here. The result is that I'm not able to run the linter using the --diff flag 🙂
Would you be open to fixing option 1 or 2 here? I'd really like to use MIGRATION_LINTER_OVERRIDE_MAKEMIGRATIONS 🙏
The text was updated successfully, but these errors were encountered:
Hi!
Thanks for creating and maintaining this. It looks useful 👍
I'm in the process of getting the linter set up for my project and have run into two small issues:
django.contrib.gis.db.backends.postgis
backend is not recognized. I think this could be mapped to postgresql safely, but I can't say for sure.sql_analyser
, but this isn't recognized when running the linter usingmakemigrations
.For the second issue, this is how config values are loaded and propagated when calling the linter management command. The same thing is unfortunately not done in the
makemigrations
management command here. The result is that I'm not able to run the linter using the--diff
flag 🙂Would you be open to fixing option 1 or 2 here? I'd really like to use
MIGRATION_LINTER_OVERRIDE_MAKEMIGRATIONS
🙏The text was updated successfully, but these errors were encountered: