-
-
Notifications
You must be signed in to change notification settings - Fork 86
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] Allow no closing djlint:on
comment
#649
Comments
Thanks, I can check that out, it's more of a bug than feature probably :) |
# [1.28.0](v1.27.2...v1.28.0) (2023-05-18) ### Bug Fixes * **formatter:** allow djlint:off to exluce the rest of a file ([17faf5f](17faf5f)), closes [#649](#649) * **formatter:** don't add blank line to empty files ([8ea5fd2](8ea5fd2)), closes [#635](#635) ### Features * **formatter:** added ability to format objects/arrays in function tags ([d446efc](d446efc)), closes [#370](#370) * **formatter:** format set blocks ([d88371c](d88371c)), closes [#646](#646)
🎉 This issue has been resolved in version 1.28.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Geez, y'all are speedy!! Thank you!! =D |
Ah, sadly this only works when there are no error codes specified x_x Will open a new ticket for that nuance =) |
Thanks, sorry I didn't think of that one, the linter logic is a bit split out. Thanks for opening another issue. |
Feature Request
Loving the idea behind this library! I'm coming from being very used to
prettier
andblack
to cut out dev time just indenting =)During my initial testing and setup though, I ran into a snag with how
djlint:off
is handled.Setup:
index.html:
Expected behavior:
djlint index.html # Should see success, no error code
Actual behavior:
The text was updated successfully, but these errors were encountered: