quarylabs/sqruff - CodSpeed

sqruff

Blog Docs Changelog

Performance History

Latest Results

refactor: derive dialect config options from struct via macro Address PR feedback: - Add dialect_config! macro that defines struct, DialectConfig impl, and DialectConfigDescriptor impl from a single declaration - Remove manual config_options() from DialectKind; config metadata is now derived from each dialect's config struct - Add DialectConfigDescriptor trait and dialect_config_options() in lib-dialects to bridge dialect configs to docs generation - Add .sqruff config file next to test fixtures showing user-facing configuration for pg_trgm https://claude.ai/code/session_017R4gsFdPF9Bw65vFiPzDUh

claude/postgres-tree-grams-setting-KzqJs

5 days ago

refactor: move LT05 comment merge test to fixtures (#2402) * refactor: move LT05 comment merge test to fixtures Move the inline test_comment_not_merged_with_next_line test from lt05.rs to the LT05.yml fixtures file as a fail/fix pair, as requested in #2352. Closes #2352 https://claude.ai/code/session_01Qq93DUgnKjmts5N1tdVX1s * chore: auto-fix formatting * fix: use multi-rule fixture for LT05 comment merge test The bug is a multi-rule interaction: LT05 moves the trailing comment correctly, but LT01 then removes the newline between the comment and code. A single-rule LT05 fixture wouldn't catch the regression. Create LT01_LT05.yml (following the CP01_CP03.yml convention) with rule: LT01,LT05 so both rules run together, and revert the incorrectly added single-rule fixture from LT05.yml. Closes #2352 https://claude.ai/code/session_01Qq93DUgnKjmts5N1tdVX1s --------- Co-authored-by: Claude <noreply@anthropic.com> Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>

main

5 days ago

Handle templater errors gracefully to prevent false positive lints (#2403) fix: prevent false positive LT01 violations when templater fails (#2354) When the dbt/jinja templater fails (e.g., no dbt project found), the linter was falling back to parsing the raw source SQL including template syntax like `{{ ref('stg_users') }}`. This caused false positive LT01 spacing violations on the `{` `{` and `}` `}` tokens. The fix: - Add error message support to SQLTemplaterError and conversion to SQLBaseError so templater errors are properly reported to users - When a templater fails in render_files_batch or render_file, record the error as a templater violation instead of silently dropping it - In parse_rendered, handle templater violations by skipping parsing (replacing the previous `unimplemented!()`) and returning the templater error as the only violation https://claude.ai/code/session_017A437S6ht899r5e3XPuJkB Co-authored-by: Claude <noreply@anthropic.com>

main

5 days ago

fix: use multi-rule fixture for LT05 comment merge test The bug is a multi-rule interaction: LT05 moves the trailing comment correctly, but LT01 then removes the newline between the comment and code. A single-rule LT05 fixture wouldn't catch the regression. Create LT01_LT05.yml (following the CP01_CP03.yml convention) with rule: LT01,LT05 so both rules run together, and revert the incorrectly added single-rule fixture from LT05.yml. Closes #2352 https://claude.ai/code/session_01Qq93DUgnKjmts5N1tdVX1s

claude/tech-debt-2352-4fiGs

5 days ago

fix: prevent false positive LT01 violations when templater fails (#2354) When the dbt/jinja templater fails (e.g., no dbt project found), the linter was falling back to parsing the raw source SQL including template syntax like `{{ ref('stg_users') }}`. This caused false positive LT01 spacing violations on the `{` `{` and `}` `}` tokens. The fix: - Add error message support to SQLTemplaterError and conversion to SQLBaseError so templater errors are properly reported to users - When a templater fails in render_files_batch or render_file, record the error as a templater violation instead of silently dropping it - In parse_rendered, handle templater violations by skipping parsing (replacing the previous `unimplemented!()`) and returning the templater error as the only violation https://claude.ai/code/session_017A437S6ht899r5e3XPuJkB

claude/fix-issue-2354-WtrY2

5 days ago

feat(postgres): add configurable pgvector extension support Add pgvector data types (VECTOR, HALFVEC, SPARSEVEC) to the PostgreSQL dialect, gated behind a `pgvector` config option following the same pattern as pg_trgm. This fixes parsing of VECTOR(N) as a proper data type with bracketed arguments, resolving the indentation bug in CREATE TABLE statements. Closes #2070 https://claude.ai/code/session_01KggBN5yWDsbETvCCYbuAWS

claude/add-pgvector-extension-CyKzm

5 days ago

chore: bump version to 0.35.4 (#2400) Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>

main

5 days ago

refactor: move LT05 comment merge test to fixtures Move the inline test_comment_not_merged_with_next_line test from lt05.rs to the LT05.yml fixtures file as a fail/fix pair, as requested in #2352. Closes #2352 https://claude.ai/code/session_01Qq93DUgnKjmts5N1tdVX1s

claude/tech-debt-2352-4fiGs

5 days ago

Active Branches

WIP: Add support for all ClickHouse builtin functions, QUALIFY and WITH FILL FROM/TO/STEP

last run

5 days ago

0%

chore: bump actions/attest-build-provenance from 3.0.0 to 4.1.0

last run

14 days ago

+3%

test(CV03): add test for unquoted multibyte identifiers

last run

1 month ago

+1%

© 2026 CodSpeed Technology

Home Terms Privacy Docs