djhtml VS prettier

We are happy to announce that DjHTML 3.0.0 has been released! This source code formatter for Django templates correctly indents mixed HTML/CSS/JS templates, including Django template tags, and can easily be used as a pre-commit hook to automatically indent Django templates on every commit.

~ djhtml -h usage: djhtml [-h] [-i] [-c] [-q] [-t N] [-o filename] [filenames ...] DjHTML is a fully automatic template indenter that works with mixed HTML/CSS/Javascript templates that contain Django or Jinja template tags. It works similar to other code-formatting tools such as Black and interoperates nicely with pre-commit. Full documentation can be found at https://github.com/rtts/djhtml positional arguments: filenames input filenames options: -h, --help show this help message and exit -i, --in-place modify files in-place -c, --check don't modify files -q, --quiet be quiet -t N, --tabwidth N tabwidth (default is 4) -o filename, --output-file filename output filename

Did you see this post a few hours ago https://www.reddit.com/r/django/comments/u1w400/linting_templates/ ? Someone suggested https://github.com/rtts/djhtml

For django templates I use djhtml: https://github.com/rtts/djhtml

https://github.com/rtts/djhtml is basic, but useful in the few things it does!

I actually wrote a tool that indents HTML files by parsing it using regexes: DjHTML

Update: the latest version of DjHTML now officially supports Jinja2!

In this post, I also use ESLint + Standard JS as my code formatting tools. Formatting JS/TS code by using ESLint is also subjective and opinionated, arguably most people would rather use Prettier instead, which provides more configurable options.

Let's be honest - setting up tools for a new project can be a frustrating process. Especially when you want to jump straight to coding part. This is often the case with ESLint and Prettier, two popular tools in the JavaScript ecosystem that can sometimes interfere with each other when it comes to code formatting. Fortunately, there's a simple solution to this process, and it's called eslint-plugin-prettier.

From my point of view, Prettier doesn't work well for styling with utility classes. For a discussion see Prettier#7863 or Prettier#5948.

Prettier: An opinionated code formatter that enforces a consistent code style.

Automating code checks with static code analysis allows us to enforce code styling effectively. By integrating tools into our workflow, we can identify errors at an early stage, while coding instead of blocking us at the end. For instance, flake8 checks Python code for style and errors, eslint performs similar checks for JavaScript, and prettier automatically formats code to maintain consistency.

So anyways, I wanted to hook up Emacs with Astro support. For now, I've just been roughing it out there and running Prettier by itself and turning off save on format and auto-complete. It's been scary.

If you're a developer, you're surely familiar with Prettier and ESLint. With over 8 years of existence, they have established themselves as references in the JavaScript ecosystem.

prettier is used to format you text

No formatting inconsistencies: The committed code should follow the organization's code formatting standards(prettier or pretty-quick).

Let’s walk through the steps for a one-time setup to configure husky pre-commit and pre-push hooks, ESLint with code styles conventions, prettier code formatter, and lint-staged. Husky automatically runs a script on each commit or push. This is useful for linting files to enforce code styles that keeps the entire code base following conventions.