Output schema type float or date rejected: unsupported_type

If your output_schema fails with the rule unsupported_type, a node has a type that is not one of the seven that Sume accepts: string, number, integer, boolean, object, array and null. Replace the type with one of those. A schema generated by a typed language is the usual source of the problem (Structured output).

Map the type to one that is allowed

format, pattern, minLength and maxLength are on the allowlist for strings. minimum, maximum, exclusiveMinimum, exclusiveMaximum and multipleOf are on it for numbers. Keywords outside the allowlist are a different violation, unsupported_keyword, and are never silently ignored.

Example

// rejected: unsupported_type at #/properties/price
"price": { "type": "float" }

// accepted
"price": { "type": "number", "minimum": 0 },
"publish_on": { "type": ["string", "null"], "format": "date" }

One check that stays on your side

A schema describes the shape Sume returns, not facts it can verify. Values such as ids, labels, captions and counts are read from what the run reported, and Sume does not verify them. Treat them as the run's own report, and validate business rules after you read output.