[psteinroe]

Stacked on #912.

Fixes formatter options and format check output that were hard to use, found in the release review.

Option errors list the valid values

$ postgres-language-server format --clause-body-style=foo a.sql
# before
Error: couldn't parse `foo`: Value not supported for clause body style
# after
Error: couldn't parse `foo`: expected 'break' or 'compact'

$ postgres-language-server format --values-row-layout=foo a.sql
# before
Error: couldn't parse `foo`: Value not supported for Layout. Use 'fit' or 'expanded'.
# after
Error: couldn't parse `foo`: expected 'fit' or 'expanded'

All formatter enums now say what they expect, without naming the Rust type. Layout is shared by --layout and --values-row-layout, and the user never sees that name.

A zero line width or indent size is rejected

--line-width=0 and --indent-size=0, and "lineWidth": 0 / "indentSize": 0 in the config file, were accepted. lineWidth and indentSize are now NonZeroU16 / NonZeroU8, as files.maxSize already is. The CLI says couldn't parse '0': number would be zero for non-zero type, the config file invalid value: integer '0', expected a nonzero u16. The JSON schema now has minimum: 1 for both.

Check output names the line

Without --write, format printed one diagnostic per statement that would change. When a statement's diff fits on one line, it is printed without line numbers, and the header only names the file. In a large file there was no way to find the statement. The message now carries the line:

a.sql format ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

  × Statement at line 4 could be formatted using `--write`

  - SELECT··x·FROM·y·WHERE·z=1;
  + select·x·from·y·where·z·=·1;

I put the line in the message rather than giving the diagnostic a span. With a span, the printer adds a code frame of the statement above the diff. When only the blank lines between statements change, the whole-file diff now says "File could be formatted" instead of "Statement".

Help shows the values

Every format flag was shown as =ARG in --help and in the CLI reference. They now show NUMBER, <spaces|tabs>, <fit|expanded> and so on, like the other options.

Docs

The layout option was described as "always breaks between clauses". Expanded layout also puts every select list item and every AND/OR operand on its own line and breaks before every CASE branch. A select-list-only subquery and a CHECK condition follow the line width instead. The option's description (and so the schema, bindings and CLI reference) and docs/features/formatting.md now say this, and the docs have an example. Together with the CASE and tabs docs in #894, this covers the docs gaps from the review.

Tests

• CLI tests for the two option errors and for rejecting zero, with the two check-output snapshots updated for the new messages.
• A configuration test for rejecting zero in the config file.
• Schema, TypeScript bindings and CLI reference regenerated with just gen-lint.

Risks

A config file with lineWidth or indentSize set to 0 used to load and now fails to load with the error above. With either set to 0 the formatter output was unusable anyway: every group broke, or nothing was indented.