-
-
Notifications
You must be signed in to change notification settings - Fork 84
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
[FEATURE]Is it possible to add a function to fix H017 automatically? #252
Comments
Its definitely a nice idea.. fix linter errors vs reformatting the entire file 👍🏽 |
Hi @christopherpickering :) Wanted to bring mdn/content#17138 to your attention in relation to this feature request. The original PR was based on H017 from djlint, with the consensus being that this is an XHTML convention that is incorrectly being applied to HTML5. Result was this pattern being removed from the remaining instances in the Mozilla Developer Network learning area in mdn/django-locallibrary-tutorial#106 and mdn/content#17149. |
Thanks for pointing that out. I agree its not needed, It's a matter of personal preference in the end. Thanks! |
Also see #372 |
Sorry for the delay, this should be in the next release. |
# [1.26.0](v1.25.1...v1.26.0) (2023-05-08) ### Bug Fixes * **blocktrans:** fixes whitespace issues on blocktrans, allows indenting on blocktrans trimmed ([249c8e8](249c8e8)), closes [#623](#623) ### Features * **formatter:** added white space cleanup for template tags ([13d0d4f](13d0d4f)), closes [#485](#485) * **linter:** added rule H037 ([6048c46](6048c46)) * **void tags:** added option to auto close void tags (linter rule H017) ([9050d30](9050d30)), closes [#252](#252)
🎉 This issue has been resolved in version 1.26.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
thank you! |
Feature Request
Djlint outputs H017 for the following code.
Tag should be self closing. (H017)
I want this to be automatically corrected as follows.
H017 happens frequently and I think it's okay to fix it automatically.
Will djlint provide the ability to fix this automatically?
The text was updated successfully, but these errors were encountered: