Skip to content

fix(djlint): recognize djlint.toml and point to the current repository - #1193

Open
monosans wants to merge 3 commits into
trunk-io:mainfrom
monosans:fix/djlint-configs
Open

monosans wants to merge 3 commits into
trunk-io:mainfrom
monosans:fix/djlint-configs

Conversation

@monosans

Copy link
Copy Markdown

I'm one of the djLint maintainers. A few things in the djlint plugin no longer match djLint:

  • Config files. djLint reads djlint.toml and .djlint.toml besides .djlintrc and pyproject.toml (added in 1.36.0, so the known good 1.36.4 has them). They're now in direct_configs, so suggest_if: config_present also suggests djlint for projects that use them.
  • Cache. djLint doesn't read .flake8, setup.cfg or tox.ini, so they no longer invalidate its cache. pyproject.toml stays.
  • Links. The repository moved from Riverside-Healthcare/djlint to djlint/djLint. The plugin README and the main README link there, and the plugin README lists the languages added since (Liquid, Tera, Askama, Mako).

Testing

The lint and fmt commands and the parse regex are unchanged, so the existing snapshots still apply. I checked the config file names against djLint's settings.py at v1.36.4 and on master. I didn't run the plugin test suite locally; CI runs it.

@trunk-io

trunk-io Bot commented Nov 15, 2026

Copy link
Copy Markdown

Merging to main in this repository is managed by Trunk.

  • To merge this pull request, check the box to the left or comment /trunk merge below.

After your PR is submitted to the merge queue, this comment will be automatically updated with its status. If the PR fails, failure details will also be posted here

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

1 participant