5 Commits

Include renames

Author	SHA1	Message	Date
Hein	5cdec88299	feat(format): expand the runtime safety gate ... 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.	2026-09-10 15:17:07 +02:00
Hein	83b215fd25	feat(format): default output to dist/examples house style ... Align the formatter defaults and layout with the hand-formatted reference procedures in dist/examples so a clean `pgtidy fmt` produces the house style. config.Default(): - align_param_types: false (no type-column alignment in param lists) - plpgsql_declare_align_type / plpgsql_declare_align_eq: true Formatter: - routine header: leading-comma params at column 0, first param at one indent, RETURNS/LANGUAGE/volatility/SECURITY each indented one level - %type / %rowtype printed tight (isPctTypeBoundary) - DECLARE = / := / DEFAULT column padded only to the widest declaration that carries an assignment - WHERE continuations in body UPDATE/DELETE: AND/OR aligned with WHERE - EXCEPTION aligned to its enclosing BEGIN; column-0 comment continuations kept flush-left Safety gate: - SemanticallyEqual tolerates CRLF vs LF inside string literals (normNL); the formatter re-emits all layout with st.Newline, so a \r\n inside a multi-line string literal is normalisation, not a code change. This was why action_init and event_exec_func previously refused to format. Corpus: - add the four CRLF reference files as idempotence/safety fixtures - regenerate test_a and test_mm_proc goldens FOR...LOOP body indentation keeps the existing +1 convention (LOOP aligned with FOR); the dist/examples use +2, so loop-body regions differ by whitespace only.	2026-09-10 14:54:20 +02:00
Hein	5cba6beeb1	fix: align PLpgSQL formatting clauses	2026-07-15 21:11:58 +02:00
warkanum	f17e87e749	fix(body): prevent joining continuation lines to comments ... * Ensure comment-only lines are flushed before adding new statements * Adjust logic to handle col-0 continuation lines correctly	2026-06-30 22:51:25 +02:00
warkanum	c8030247f2	chore: more work done and planning with AI.	2026-06-30 22:43:25 +02:00