Replace the bare SemanticallyEqual call in every frontend (CLI fmt, LSP
formatting + rangeFormatting) with format.VerifySafe, which runs four
checks before any formatted output is emitted:
- semantic equivalence - the code token stream is unchanged
- comment preservation - no -- or /* */ comment is dropped, merged,
split, reordered, or reworded (line endings / indentation normalised
away; recurses into dollar-quoted bodies)
- structural balance - the () [] and BEGIN/CASE/IF/LOOP...END nesting
profile matches, ignoring anything inside a comment or a string
- idempotence - a second format pass would not change it
On failure the CLI now prints the specific reason and keeps the original.
The comment check surfaced two real formatter bugs, both fixed in
formatBodyStatements:
- multi-line /* */ comments inside a PL/pgSQL body had their interior
lines re-split and reindented as if they were statements; they are
now tracked and carried verbatim with the opening line
- a column-0 -- line was glued onto the preceding line by the
split-line-join, which merged consecutive comment lines into one
Regenerate testdata/corpus/test_mm_proc.pgsql (was carrying the mangled
output). TestCorpusIdempotentAndSafe now runs the full VerifySafe bundle;
add safety_test.go with targeted cases.
16 KiB
PgTidy — TODO / Progress
Tracks what is done and what remains. See plan.md for the full design and rationale.
Legend: ✅ done · 🚧 in progress · ⬜ not started
V1 — Formatter + CLI (current milestone)
✅ Scaffold module + repo hygiene
go.mod(module git.warky.dev/wdevs/pgtidy, go 1.26).- Replaced WkMailSync boilerplate:
AGENTS.md(PgTidy architecture + invariants),CLAUDE.md,Makefile(build/test/vet/fmt/lint/clean). - Directory layout created (
cmd/,pkg/...,testdata/). - Copied 4 real-world procedures into
testdata/corpus/*.pgsql(safety harness).
✅ Lossless lexer — pkg/lexer
token.go:Kindenum (trivia, words, literals, operators, punctuation) +Token.lexer.go: full PG token coverage — dollar-quoted strings ($tag$, nested-tag aware),--/ nestable/* */comments, standard/escape/bit/hex/unicode strings, numbers (decimal, exponent, leading dot,0x/0o/0b,_separators), positional params ($1), operator runs with PostgreSQL's trailing+/-rule,::/:=/:, punctuation. Tracks line/col per token.lexer_test.go: unit tests (kinds, operator trailing rule, dollar quotes, line/col) + corpus round-trip assertingemit(Lex(src)) == srcbyte-for-byte.- Status: all tests pass; round-trips all 4 corpus files. Invariant #1 satisfied.
✅ CST node model + parser — pkg/cst, pkg/parser
pkg/cst: lossless node model —Tok(significant token + leading trivia),Attach,File.Source()(byte-exact reconstruction),Raw(verbatim fallback),CreateFunction(Head/Name/Params/Options/As/Body/Tail/Semi),Param(with separator comma).pkg/parser: statement splitting at top-level;; structures CREATE FUNCTION/PROCEDURE (head, qualified name, comma-split params, option clauses split by keyword, AS + body); everything else →Raw. Graceful degradation is a property of the data model.parser_test.go: small round-trips, CreateFunction shape assertions, Raw fallback, and corpus round-trip — reconstructs all 4 files byte-for-byte; structures all 4 functions.- Status: all tests pass.
- Still TODO (later): DML/other-DDL structuring (currently Raw) for full formatting.
🚧 PL/pgSQL body parser ← NEXT (the remaining V1 piece)
✅ DECLARE section — pkg/format/body.go
formatBodysplits the dollar-quote tag, callsformatBodyInner.formatBodyInnerlocatesDECLAREandBEGINat depth 0, formats the declare block, then emitsBEGINonwards verbatim.formatDeclareVars: each variable declaration collapsed to one line (name type [= expr];),--Block--comment markers preserved on their own lines, mid-declaration block comments trigger verbatim fallback.needSpacefixed forLBracket— no space before[after ident/closing bracket (fixescitext[], array subscripts).semanticallyEqualin tests updated to recurse into dollar-quoted body tokens so whitespace normalization inside the body does not falsely fail the semantic check.- Added
testdata/corpus/test_a_broken.pgsql— a CRLF corpus file with intentionally broken layout (split-line variables + split-line body statements) used as a formatting target;testdata/corpus/test_a.pgsqlis the golden output. - Status: all tests pass; DECLARE section formats correctly.
✅ Body statement formatter — pkg/format/body.go
formatBodyStatements: line-by-line formatter for theBEGIN … ENDblock.- Block-depth tracker:
BEGIN/END,IF/THEN/ELSIF/ELSE/END IF,LOOP/END LOOP,EXCEPTION. - Split-line join: col-0 lines at paren-depth 0 with non-clause first token are joined to preceding line. SQL clause keywords (
SELECT,FROM,WHERE,INTO,WITH,HAVING,GROUP,ORDER,RETURNING,SET, joins) stay on own lines. - Base-indent normalisation: first logical line of each statement gets
blockDepth × st.Indent; subsequent lines preserve their original indentation (relative indentation maintained for multi-line expressions). - Blank-line count preservation: blank lines between statements kept as-is.
- Verbatim-indent mode after
EXCEPTION: original leading whitespace preserved to avoid style conflicts between functions that putWHENat col-0 vs indented. sqlClauseKwmap;firstBodyKeyword,leadingWhitespacehelpers.TestFormatBodyBroken: golden-file test —format(test_a_broken.pgsql)must equaltest_a.pgsql.- Updated
test_a.pgsqlto match actual formatter output. - Status: all tests pass; idempotence verified.
✅ Printer + style config — pkg/format, pkg/config
pkg/config:Stylestruct +Default()= house style.Load(startDir)walks up the directory tree to find.pgtidy.yamland merges its fields over the defaults. Supported keys:indent,newline,keyword_case,ident_case,type_case,commas. Dependency:gopkg.in/yaml.v3.pkg/format: formats CREATE FUNCTION/PROCEDURE headers to house style (params one-per-line leading-comma, option clauses each on own line, AS/$$own lines); DECLARE section formatted (see body parser entry);Rawstatements emitted verbatim. Spacing engine (needSpace, tight ops:: : -> ->>, array[]) + casing (keywords/typeNamessets). Comment-safety: verbatim fallback if a header carries comments it cannot relocate.pkg/format/body.go: DECLARE section formatter (see body parser entry).- Tests: golden header, idempotence, corpus idempotence + semantic equivalence (updated to recurse into dollar-quoted body tokens).
- Note: not a full Wadler Doc-IR yet — fixed-layout printer. Doc-IR for width-based expression wrapping can come when DML structuring lands.
✅ CLI fmt + safety harness — cmd/pgtidy
pgtidy fmt(gofmt model): default stdin→stdout;-w/--write,-l/--list,--check(CI exit codes);-d/--diff(unified diff output);version/help.- Config discovery: walks up from cwd to find
.pgtidy.yaml; applied before formatting. diff.go: in-house unified diff (LCS-based, zero additional deps).fmt_test.go: stdin, --check (un/formatted), -w idempotence, unknown-command.- Safety invariants #2 (semantic equivalence), #3 (idempotence), #4 (graceful degradation)
are tested in
pkg/formatover the corpus. - Runtime safety gate (
format.VerifySafe,pkg/format/safety.go): every frontend runs it before emitting. BundlesSemanticallyEqual(code token stream) +CommentsPreserved(no comment dropped/merged/split/reworded, recursing into bodies) +StructurallyBalanced(()[]/ BEGIN·CASE·IF·LOOP…END profile, ignoring comment & string contents) + an idempotence re-format. On failure the CLI prints the reason and keeps the original. Caught two real bugs: multi-line/* */bodies were reindented as code, and col-0--lines were glued onto the previous line (merging consecutive comments) — both fixed informatBodyStatements.
✅ V2 — Linter
pkg/pgast:go-pgquery(WASM, no cgo) wrapper → real PG AST.FirstTokenOffsetskips leading whitespace/comments for accurate line numbers.pkg/diagnostics:Diagnostic{RuleID, Severity, Message, File, Line, Col}.pkg/lint:Engine,Ruleinterface,New()with all built-ins:- MIG001 CREATE INDEX without CONCURRENT
- MIG002 ALTER TABLE ADD COLUMN NOT NULL without DEFAULT
- MIG003 ALTER TABLE ADD CONSTRAINT FK/CHECK without NOT VALID
- COR001 SELECT * | COR002 UPDATE without WHERE | COR003 DELETE without WHERE
- NAM001/2/3 table/column/function names not snake_case (quoted identifiers only)
pgtidy lint [--only=ID,...] [files...]; exits 1 on findings, 2 on error.- Fixture SQL in
testdata/lint/; 6 tests covering violations + clean fixtures. --fixrewrites files in place applying autofixes; for stdin, prints fixed SQL to stdout.- Autofixable: MIG001 (insert
CONCURRENTLYafterINDEX) and MIG003 (insertNOT VALIDbefore;). MIG002, COR*, NAM* are intentionally not autofixable. pkg/diagnostics.TextFix{Offset, End, New, Title}— byte-range replacement attached toDiagnostic.Fix.pkg/lint.ApplyFixes— applies all fixes in reverse-offset order; overlapping fixes skipped.- Fix helpers (
mig001Fix,mig003Fix) handle pg_query's convention ofStmtLenexcluding the trailing;.
✅ V3 — LSP + VSCode
pkg/lsp: JSON-RPC 2.0 over stdio;textDocument/formatting(full document),publishDiagnosticson every open/change,textDocument/codeActionquick-fixes, lifecycle (initialize/shutdown/exit). No external deps.cmd/pgtidy/lsp.go:pgtidy lspsubcommand; config discovered from cwd.editors/vscode/: TS extension usingvscode-languageclient; launchespgtidy lspvia stdio;.pgsqlmapped tosqllanguage;pgtidy.path/pgtidy.enablesettings.- Range formatting: future.
- Full capability inventory, runtime-verified gaps, and ranked next steps in
docs/lsp-status.md(issue #3).
✅ V4 — DataGrip
editors/datagrip/: Gradle-based JetBrains plugin targeting DataGrip 2024.3+ via LSP4IJ.build.gradle.kts/settings.gradle.kts/gradle.properties— IntelliJ Platform Gradle Plugin v2.plugin.xml— registersPgTidyServerFactoryas an LSP4IJ<server>extension and maps*.sql/*.pgsqlto it.PgTidyServerFactory.kt+PgTidyServerConnection.kt— launchespgtidy lspviaProcessStreamConnectionProvider.- Requires LSP4IJ plugin installed in the IDE;
pgtidybinary on PATH.
✅ Build / release (cross-cutting)
.goreleaser.yaml: multi-platform matrix — linux/darwin × amd64/arm64 + windows/amd64; no CGO; ldflags version injection; draft GitHub release.Makefileextended:snapshot(local multi-platform build),release(publish),vscode-compile,vscode-package..github/workflows/ci.yml: test + vet + gofmt check + goreleaser snapshot on every push/PR..github/workflows/release.yml: goreleaser publish + VSCode.vsixartifact onv*tag.make_release.shretained from boilerplate.
Core invariants (must always hold — tested)
- ✅ Lossless lex:
emit(Lex(src)) == src(corpus round-trip). - ✅ Semantic equivalence: formatting changes only trivia/layout (corpus token-stream check).
- ✅ Idempotence:
fmt(fmt(x)) == fmt(x)(corpus + CLI tests). - ✅ Graceful degradation: unparsable spans pass through verbatim (Raw nodes + verbatim body).
✅ DML statement formatting (top-level)
pkg/format/dml.go:formatDMLformats top-level SELECT/INSERT/UPDATE/DELETE/WITH.- Clause-per-line layout at depth-0 boundaries; handles: SELECT, FROM, WHERE, HAVING, GROUP BY, ORDER BY, LIMIT, OFFSET, RETURNING, JOIN variants (LEFT/RIGHT/INNER/FULL/ CROSS/NATURAL, optional OUTER), ON CONFLICT, UNION/INTERSECT/EXCEPT, SET, VALUES, INSERT INTO, DELETE FROM, WITH (including multi-CTE bodies).
- SELECT, SET, and RETURNING bodies formatted as leading-comma column lists.
- Keywords inside subqueries (paren depth > 0) cased correctly via
dmlInline. needSpace: addedparenKwsset (AS, EXISTS, IN, NOT, LIKE, ILIKE, SIMILAR) so these keywords get a space before(instead of the no-space function-call rule.- Printer
writeItem: detects DML-starting Raw nodes and routes toformatDML. - Tests: 13 targeted golden tests + idempotence sweep in
pkg/format/dml_test.go. - Note: table name before
(in INSERT column list is indistinguishable from a function call at the token level — formatted without space (known limitation). - Note: SQL keywords inside PL/pgSQL function bodies remain lowercase (matching the corpus golden files); casing is applied only to top-level DML.
- Still TODO: Wadler Doc-IR printer for width-aware wrapping of long lines.
- Still TODO: LSP range formatting.
✅ Config expansion — DataGrip settings parity
Reference: PostgresCodeStyleSettings mapping in docs/plan.md.
✅ Extended pkg/config fields
Added to Style struct, yamlFile, and Load() in pkg/config/config.go:
- New types:
WrapMode(always|when_long|never),Placement(same_line|new_line) - Casing:
AliasCase,BuiltinCase,CustomTypeCase— all defaultlower - Query layout:
AlignColumns,AlignLineComments,SelectAlignAs,SetAlignEqual,IndentJoin,JoinIndentSize,WhereWrap,WhereAndOrIndent - Subqueries:
SubqueryOpening,SubqueryContent,SubqueryClosing,SubquerySpaceBeforeParen - INSERT:
InsertCollapseValues - Routines:
AlignParamTypes,RoutineAsWrap - PL/pgSQL:
PlpgsqlMaxBlankLines,PlpgsqlDeclareAlignType,PlpgsqlDeclareAlignEq,PlpgsqlIfThenNewline,PlpgsqlLoopCollapse - Expressions:
BinaryOpAlign,SpaceAfterCommaInCalls,CaseWhenWrap,CaseEnd,CaseCollapse,RecordSpaceBeforeParen docs/config/default.pgtidy.yamlupdated with all new keys and comments.
✅ Casing engine — alias and built-in classification
pkg/format/keywords.go: added builtinFunctions set (COALESCE, MAX, MIN, NOW, …).
pkg/format/format.go: caseTextCtx uses context — prev token and nextIsLParen flag
to route ident tokens through AliasCase (after AS) or BuiltinCase (before ().
inline() and dmlInline() pass context to caseTextCtx.
✅ Formatter — query layout settings (pkg/format/dml.go)
indent_join+join_indent_size: JOIN clause indented byJoinIndentSize × Indent.where_wrap+where_and_or_indent:dmlWhereClausesplits AND/OR conditions;alwaysputs each condition on its own line indented under WHERE;neverkeeps inline.set_align_equal:dmlColListSetpads LHS of SET items so=signs align.align_columns+select_align_as:dmlColListSelect+alignSelectItemspads SELECT expressions so AS keywords and aliases align vertically.space_after_comma_in_callsapplied indmlInline.binary_op_alignregistered in config (enforcement in WHERE/expression context deferred).
⬜ Formatter — subquery formatting
subquery_opening/content/closing/space_before_paren fields are wired in config.
Enforcement in dml.go is not yet implemented — subqueries use current CTE formatting
as a proxy (new_line for content, inline for single-arg subexpressions).
⬜ Formatter — INSERT VALUES collapse
insert_collapse_values field is wired in config. Enforcement in dml.go not yet implemented.
✅ Formatter — routine param alignment (pkg/format/format.go)
align_param_types:alignParamTypes()pads param names so type columns align; defaultfalse(house style: no type-column alignment in param lists).routine_as_wrap: whenfalse, AS stays on the same line as the last option clause.- Golden file
testdata/corpus/test_a.pgsqlupdated to reflect aligned params.
✅ Formatter — PL/pgSQL body settings (pkg/format/body.go)
plpgsql_max_blank_lines: blank-line runs capped at the configured limit; default1.plpgsql_declare_align_type+plpgsql_declare_align_eq: two-pass declare formatter measures name/type widths then pads for alignment;writeDeclareAlignedhelper. Both defaulttrue(house style). The=column is padded only to the widest type among declarations that actually carry an assignment, so a lonex text = '…';stays tight.plpgsql_if_then_newline: whenfalse,joinThenToConditionmerges THEN onto the preceding condition line.plpgsql_loop_collapse:tryCollapseLoopdetects empty FOR/WHILE loop bodies and collapses them to one line.- CRLF normalization in trivia emission (comment text, body trivia before DECLARE).
⬜ Formatter — expression settings (case_when_wrap, case_end, case_collapse, record_space_before_paren)
Config fields wired. Expression-level CASE/ROW formatting not yet implemented.
⬜ DataGrip XML import/export (optional, V4+)
pgtidy config import --datagrip <settings.xml> / pgtidy config export --datagrip
not implemented.
Open risks
go-pgquerytracks PG17 (not PG18) — fine for lint; irrelevant to formatter path.- Leading-comma + one-per-line is a first-class style option, not an afterthought.