Boeing/config-file-validator

Problem cfv preserves multiple consecutive blank lines between mapping entries instead of collapsing them to one: # input (2 blank lines): 1: 2 3: 4 # cfv output (wrong — keeps both blanks): 1: 2 3: 4 # expected (collapse to 1 blank): 1: 2 3: 4 Reproduction Create a file test.yaml: first: 1 second: 2 third: 3 Run: cfv format --fix --no-config test.yaml cat test.yaml Actual: multiple blank lines preserved. Expected: at most one blank line between any two mapping entries. Root cause pkg/formatter/yamlfmt/printer.go — collapseConsecutiveBlankLines exists but is not catching all cases. Likely an off-by-one in the newline counting logic (3+ consecutive TokNewline should reduce to 2 = one blank line).

Problem cfv normalizes YAML quoted scalars to single quotes when no escape sequences are present: # input: "*v1.Proxy.gateway-proxy_gloo-system": reportedBy: gloo # cfv output (wrong — switches to single): '*v1.Proxy.gateway-proxy_gloo-system': reportedBy: gloo # expected (keep double): "*v1.Proxy.gateway-proxy_gloo-system": reportedBy: gloo Correct rule The quote decision should follow this cascade: Content has escape sequences (\n, \t, etc.) → keep original quote style Content contains a literal " → use single quotes Content contains a literal ' → use double quotes Otherwise → use double quotes (default) cfv currently picks single quotes at step 4. It should pick double. Reproduction Create a file test.yaml: "*v1.Proxy.gateway-proxy": state: Accepted "normal-key": value: 123 Run: cfv format --fix --no-config test.yaml cat test.yaml Actual: both keys switched to single quotes. Expected: both keys stay as double quotes (rule 4 — no embedded quotes, default to

Problem When a TOML inline table contains an array that was multiline in the source, cfv preserves the multiline form: reqwest = { workspace = true, default-features = false, features = [ "rustls", ] } Inline tables must appear on a single line (TOML v1.0 §5.2). The correct output: reqwest = { workspace = true, default-features = false, features = ["rustls"] } Reproduction Create a file test.toml: [dev-dependencies] reqwest = { workspace = true, default-features = false, features = [ "rustls", ] } Run: cfv format --fix --no-config test.toml cat test.toml Actual: multiline array preserved inside the inline table. Expected: array collapsed to features = ["rustls"] on one line. Root cause pkg/formatter/tomlfmt/printer.go — the inInlineTable flag exists but does not force nested arrays to single-line when the source had them multiline. Fix When inInlineTable == true, always print nested arrays in compact single-line form regardless of their source layout.

Problem cfv collapses short JSON arrays to a single line when they fit within printWidth: "brackets": [["{", "}"], ["[", "]"], ["(", ")"]], The correct behavior is to always expand non-empty arrays (one element per line): "brackets": [ ["{", "}"], ["[", "]"], ["(", ")"] ], Empty arrays [] and empty objects {} stay on one line. Everything else expands. Reproduction Create a file test.json: {"brackets": [["{", "}"], ["[", "]"], ["(", ")"]],"other": [1, 2, 3]} Run: cfv format --fix --no-config test.json cat test.json Actual: inner arrays collapse to [["{", "}"], ...] on one line. Expected: each inner array on its own line. Root cause pkg/formatter/jsoncfmt/jsonc.go — isInlineArray returns true when prefixLen + valLen <= maxLineWidth. This logic should be removed for JSON arrays. Non-empty arrays always expand.

We're preparing the v3.0.0 release and want real-world feedback before it goes stable. We want to try it out in your projects, break it, tell us what happened. Install the RC go install github.com/Boeing/config-file-validator/v3/cmd/[email protected] Or download a binary from the release page for macOS, Linux, or Windows. What's new in v3 New CLI: cfv check, cfv format, cfv format --fix Formatting capabilities with --fix for 9 formats (JSON, JSONC, YAML, TOML, HCL, XML, INI, Properties, ENV) Schema validation via SchemaStore auto-lookup Gitignore-aware file discovery (--gitignore) Known-filename detection (Pipfile, Cargo.lock, tsconfig.json, .clang-format, etc.) Sort keys (--sort-keys) for YAML, JSON, JSONC, TOML, Properties, INI Formatting docs: https://github.com/Boeing/config-file-validator/blob/feat/3.0/website/docs/guides/formatting.md Try it instead of your usual tools Run cfv format --diff . on a repo you normally format with prettier, yamlfmt, taplo, or terraform fmt. Compare th