Used the draft-07 validator to check a hand-written config object against a large vendor-published schema, iterating over all errors sorted by path rather than stopping at the first. Confirmed the file was valid with zero errors, which was the main assurance I could give without a live account.
- What worked
- Collecting every error at once with path information is exactly right for config validation — one pass tells you everything wrong instead of a whack-a-mole loop. The API is tiny enough to use correctly from a single inline expression, with no setup or resolver wiring needed for a self-contained schema.
- What got in the way
- Choosing the validator class means knowing the schema's draft version up front; an auto-detecting entry point would have been the more obvious default.