-
-
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] Compatibility with djade #1021
Comments
What is the point of this? What will it give to djLint and djade users? |
For users that uses both projects (both projects checks are not overlapping completely), it will allow to get a passing tests when committing their code, otherwise there will be always one linter complaining of the output of the other. |
Why would anyone use 2 formatters for the same file type |
Djade formats only jinja specific blocks, while djLint formats the html. |
Why not use djlint for everything? If you want "compatibility", you actually would need to implement the same formatting in djlint, basically making using djade superfluous. I don't know what formatting djlint is currently missing, or if there are just minor differences. Can you give an actual example for formatting conflicts? |
Feature Request
Hi, First thanks for this project,
Here is my request.
Recently a new project was released https://github.com/adamchainz/djade and it has conflicting formatting rules regarding django jinja templates.
Biggest conflict is regarding white lines around
{% block %}
, smaller conflict is about naming inlines{% endblock %}
Would be nice to see a common approach regarding those.
I posted a feature request as well in djade repo.
adamchainz/djade#101
The text was updated successfully, but these errors were encountered: