The config that silently fails to parse
A YAML file with a tab instead of spaces, or an INI line missing its delimiter, often fails only at runtime — sometimes on one machine and not another. These are the bugs that slip past a quick eyeball.
Scan it first
Paste the text into the Config Linter. It flags tabs in indentation, trailing whitespace, and lines that do not match key: value or key = value. Fix the flagged lines before you commit.
Worked example
name: app / port:8080 / debug: true — the linter flags the third line: it is indented under nothing and looks like a mapping child without a parent mapping, a classic YAML mistake.
Boundaries
- Heuristic checks only — it is not a full YAML/INI parser.
- Validate critical configs with the official parser or schema as well; the linter catches the common cosmetic causes, not every semantic error.
FAQ
Does it support JSON or TOML? Focus is YAML/INI; for JSON use the JSON Formatter, for TOML validate with a dedicated parser.
Why care about trailing spaces? They are invisible but can break strict parsers and diffs.