You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, ajv can only validate custom formats that have a string data type. This limits validation for epsg-code, temporal-intervals and other formats that are of type array, object or integer. We need to either help improve ajv (see ajv-validator/ajv#1039) or change the processes to use custom JSON schema keywords (see https://github.com/Open-EO/openeo-processes/issues/67). See jsonschema.js for related comments in the code.
Currently, ajv can only validate custom formats that have a string data type. This limits validation for epsg-code, temporal-intervals and other formats that are of type array, object or integer. We need to either help improve ajv (see ajv-validator/ajv#1039) or change the processes to use custom JSON schema keywords (see https://github.com/Open-EO/openeo-processes/issues/67). See jsonschema.js for related comments in the code.
Related issue: json-schema-org/json-schema-spec#759
The text was updated successfully, but these errors were encountered: