Skip to content

docs(site): print the homepage's convert output one clause per line - #126

Merged
kvlonge merged 1 commit into
mainfrom
docs/layout-recapture
Nov 6, 2026
Merged

kvlonge merged 1 commit into
mainfrom
docs/layout-recapture

Conversation

@kvlonge

@kvlonge kvlonge commented Nov 6, 2026

Copy link
Copy Markdown
Contributor

Follow-up to #124 (D265). Every convert output printed on the homepage, re-run on main ff9ff20 in a fresh folder with no sqlquack.toml (section 04 uses the repository's sqlquack.toml with hash set to warn):

  • Hero: sqlquack convert revenue.sql --schema schema.json now prints SELECT on its own line with 4-space items, and the summary reads "done, converted under the built-in default" (since feat: use the built-in policy when there is no policy file #120).
  • 02 decimal: same layout, still trimmed with …
  • 03 HASH refusal: the help line is the one the built-in policy prints now ("the built-in policy refuses every known divergence; pass --policy with a policy file that allows hash …").
  • 04 HASH under a policy that allows it: same layout, still trimmed.
  • echo "SELECT 1 AS total" | sqlquack convert stays on one line (60 characters or fewer).

The docs pages (index, quickstart, convert, python) were already updated in #124 and match the real output.

Checks: build_engine, build, check_figures, check_links (17 pages, 0 broken), test:engine 7/7, generate_diagnostics --check. The playground was checked at 1280 and 390 against this build with DuckDB-WASM: valid and decimal pass all four stages, and the rows equal the --compact output run in native DuckDB.

Re-run on main ff9ff20 in a folder with no sqlquack.toml: the hero, the
decimal and HASH examples now show the clause-per-line layout, the hero's
summary names the built-in default, and the HASH refusal's help line is the
one the built-in policy prints.
@kvlonge
kvlonge merged commit d19c7a5 into main Nov 6, 2026
1 of 2 checks passed
@kvlonge
kvlonge deleted the docs/layout-recapture branch November 9, 2026 21:31
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant