Machine-readable reason, safe to branch on.
OptionalexpectedWhat the schema asked for, when meaningful (e.g. "number").
OptionalmaximumThe upper bound that was violated, on a too_big issue — the maximum
length, element count or numeric value the constraint allows.
Human-readable description. Matches the legacy errors[] strings.
OptionalminimumThe lower bound that was violated, on a too_small issue — the minimum
length, element count or numeric value the constraint allows.
Dotted path to the offending value, e.g. "address.city" or
"tags[2]". Empty string when the failure is about the root value.
OptionalreceivedWhat was actually found, when meaningful (e.g. "string").
OptionalvalueThe offending value itself, when the constraint is about the value rather than a property of it.
Treat as sensitive. A numeric bound is exactly what guards PINs,
one-time codes and amounts, so the value is deliberately kept out of
message and out of the Standard Schema output — the two places an
issue is most likely to be logged or forwarded wholesale. Read it
explicitly when you want to show it.
A single, structured validation failure.
One failed
parsecan produce many issues — validation collects every problem rather than stopping at the first.