[jviotti]

Signed-off-by: Juan Cruz Viotti jv@jviotti.com

[augmentcode]

🤖 Augment PR Summary

Summary: Adds linting to catch OpenAPI schema examples that fail validation.
Introduces valid_example for OpenAPI 3.0, 3.1, and 3.2 vocabularies.
Uses exhaustive evaluation for standalone and embedded schemas.
Reports validation messages with instance locations and evaluation paths.
Removes invalid examples with --fix, while skipping OpenAPI 3.0 $ref siblings.
Updates vendored Blaze and CLI rule-list expectations for the additional rule.

_{🤖 Was this summary useful? React with 👍 or 👎}

[augmentcode]

Review completed. 2 suggestions posted.

Comment augment review to trigger a new review at any time.

[augmentcode]

At vendor/blaze/src/alterschema/linter/valid_example.h:29, could you check an XML example such as {"type":"object","example":"<pet/>"}? OpenAPI 3.0 explicitly permits string-encoded non-JSON examples, but this value is passed unchanged to JSON validation, so lint flags it as a type mismatch and --fix deletes a permitted example.

Severity: medium

_{🤖 Was this useful? React with 👍 or 👎, or 🚀 if it prevented an incident/outage.}

[augmentcode]

At vendor/blaze/src/alterschema/linter/valid_example.h:73–74, could you check an OpenAPI 3.0 request schema with required: [id], properties: {id: {type: integer, readOnly: true}}, and example: {}? That example is valid because the requirement applies only to responses, but the compiler ignores readOnly and enforces every required entry, causing lint to reject it and --fix to delete it; response examples omitting required writeOnly fields have the same problem.

Other locations where this applies: vendor/blaze/src/alterschema/linter/valid_example.h:47–48

Severity: medium

Other Locations

• vendor/blaze/src/alterschema/linter/valid_example.h:47

_{🤖 Was this useful? React with 👍 or 👎, or 🚀 if it prevented an incident/outage.}