UnknownPlatypus/djangofmt - CodSpeed

UnknownPlatypus

djangofmt

Blog Docs Changelog

Performance History

Latest Results

fix(playground): Enable getrandom wasm_js backend for the wasm build The `unsorted-tailwind-classes` rule pulls in `rustywind_core`, which depends on `ahash` -> `getrandom` 0.3. getrandom refuses to compile for wasm32-unknown-unknown unless its Web Crypto backend is selected, breaking the playground build (it exposes `lint()` via `check_ast`). Enable getrandom's `wasm_js` feature for the wasm target. Since getrandom 0.3.4 the feature alone selects the backend, so the `getrandom_backend="wasm_js"` RUSTFLAGS/cfg (and the `.cargo/config.toml` carrying it) is no longer needed. getrandom is never referenced in our code, so add it to cargo-shear's ignore list.

rustymind

4 hours ago

fix(playground): Enable getrandom wasm_js backend for the wasm build The `unsorted-tailwind-classes` rule pulls in `rustywind_core`, which depends on `ahash` -> `getrandom` 0.3. getrandom 0.3 refuses to compile for wasm32-unknown-unknown unless its JS backend is selected, breaking the playground build (it exposes `lint()` via `check_ast`). Enable getrandom's `wasm_js` feature for the wasm target and set the matching `getrandom_backend="wasm_js"` cfg via `.cargo/config.toml` (both are required).

rustymind

21 hours ago

feat(lint): Support custom Tailwind prefix for unsorted-tailwind-classes Recognize a project-configured Tailwind prefix when sorting classes, so prefixed utilities (`ds-text-white`, `tw:flex`, …) are ordered canonically instead of being treated as unknown classes and left unsorted. Configured per-rule, mirroring ruff's per-linter option sections: [tool.djangofmt.lint.unsorted-tailwind-classes] prefix = "tw-" # Tailwind v3; use "tw:" for v4 rustywind already supports prefix-aware sorting (avencera #136), so this threads the option through the pyproject loader and the linter Settings.

rustymind

21 hours ago

ci(codspeed): pin glibc CPU-feature dispatch to reduce benchmark variance (#366)

main

22 hours ago

ci(codspeed): pin glibc CPU-feature dispatch to reduce benchmark variance

ci/codspeed-glibc-tunables

22 hours ago

feat(lint): Add duplicate-block-name lint rule ## What it does Checks for multiple `{% block %}` tags that share the same name within a single template. ## Why is this bad? Django requires `{% block %}` names to be unique within a template. A block both provides a hole for a child template to fill and defines the default content for that hole, so two blocks with the same name are ambiguous. Django raises a `TemplateSyntaxError` when the template is parsed, so a duplicate name breaks the template at runtime. ## Example ```html {% block title %}Title 1{% endblock %} {% block title %}Title 2{% endblock %} ``` Use instead: ```html {% block title %}Title 1{% endblock %} {% block subtitle %}Title 2{% endblock %} ``` ## References - [Django documentation: template inheritance](https://docs.djangoproject.com/en/stable/ref/templates/language/#template-inheritance)

main

1 day ago

Add `duplicate-block-name` lint rule ## What it does Checks for multiple `{% block %}` tags that share the same name within a single template. ## Why is this bad? Django requires `{% block %}` names to be unique within a template. A block both provides a hole for a child template to fill and defines the default content for that hole, so two blocks with the same name are ambiguous. Django raises a `TemplateSyntaxError` when the template is parsed, so a duplicate name breaks the template at runtime. ## Example ```html {% block title %}Title 1{% endblock %} {% block title %}Title 2{% endblock %} ``` Use instead: ```html {% block title %}Title 1{% endblock %} {% block subtitle %}Title 2{% endblock %} ``` ## References - [Django documentation: template inheritance](https://docs.djangoproject.com/en/stable/ref/templates/language/#template-inheritance) Closes #361

feat/duplicate-block-name

1 day ago

Add `duplicate-block-name` lint rule ## What it does Checks for multiple `{% block %}` tags that share the same name within a single template. ## Why is this bad? Django requires `{% block %}` names to be unique within a template. A block both provides a hole for a child template to fill and defines the default content for that hole, so two blocks with the same name are ambiguous. Django raises a `TemplateSyntaxError` when the template is parsed, so a duplicate name breaks the template at runtime. ## Example ```html {% block title %}Title 1{% endblock %} {% block title %}Title 2{% endblock %} ``` Use instead: ```html {% block title %}Title 1{% endblock %} {% block subtitle %}Title 2{% endblock %} ``` ## References - [Django documentation: template inheritance](https://docs.djangoproject.com/en/stable/ref/templates/language/#template-inheritance) Closes #361

feat/duplicate-block-name

1 day ago

Latest Branches

-75%

feat(lint): Add `unsorted-tailwind-classes` lint rule#332

21 hours ago

81fa99f

rustymind

0%

ci(codspeed): pin glibc CPU-feature dispatch to reduce benchmark variance#366

1 day ago

1dec5eb

ci/codspeed-glibc-tunables

-12%

feat(lint): Add `duplicate-block-name` lint rule#365

1 day ago

bcc8ab7

feat/duplicate-block-name

© 2026 CodSpeed Technology

Home Terms Privacy Docs