-
-
Notifications
You must be signed in to change notification settings - Fork 166
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Remove Precommits #391
Remove Precommits #391
Conversation
Dependency Review✅ No vulnerabilities or license issues or OpenSSF Scorecard issues found.OpenSSF Scorecard
Scanned Manifest Files |
08e12d6
to
889fcba
Compare
|
Maybe better solution would be to keep just basic ones like black, djlint/prettier and mypy. I would also consider swapping djLint to Prettier it's much more popular, active and up to date in compare to djLint and covers more formats like css/js/md/yaml. I could implement that but for that to work HTML code need to be fixed because it's a mess, double quotes used everywhere like here
this cause problems for linting/formatting tools. |
Does prettier support Django templates though @Domejko? |
There is jinja2 plugin. |
Ah I see. I still think that precommit are a bad idea though, especially for mypy. At least black and djlint will run in the background without disturbing you. Whereas a mypy test will fully block you. That's the thing I don't want |
Hmm so we could leave it with just Black and for djLint change command to --format instead of --check (to avoid getting blocked by djLint errors) and I could start working on replacing djLint with Prettier but it will take some time since there are dozens of errors in html that have to be fixed before it will be able to run properly. |
Is there any direct issues with djlint though? I've found it to work wonders. You can also change config to make " turn into single ' but I just had it off cause it's habit to use double quotes lol. We can change some config to make it better, it's a great tool |
(moved to #395) |
I believe pre-commits are a nightmare. They slow down development, sometimes cause issues that fully block users from committing (have done this to me many times!) and just don't seem worth it.
We have PR status checks that will block things like linting issues. I'd rather allow users to commit and then guide them to fix issues rather than not letting them commit and be stuck on their own.