{"version":"2.1.260","anchor":"ajv-validation-error-messages-now-include-actual-values","canonical_anchor":"ajv-validation-error-messages-now-include-actual-values","heading":"Ajv validation error messages now include actual values","tier":"notice","area":"Structured Output","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.260\/e\/ajv-validation-error-messages-now-include-actual-values","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.260","markdown":"### Ajv validation error messages now include actual values\n\nValidation error messages now show the actual value that violated a schema constraint.\n\nStructuredOutput validation error messages for `minLength`\/`maxLength`, `minItems`\/`maxItems`, `minProperties`\/`maxProperties`, `enum`, and `const` violations now include the actual observed value or count, for example \"(got 5)\", instead of a bare Ajv message.\n\n- Area: Structured Output\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5"}