Not sure if this is the right repo but feels like the closest - feel free to move. I haven't investigated this much other than reproducing as it may have something to do with an upstream issue in the validator itself.
Given the following schema
{
"id": {
"type": "string",
"format": "uuid"
}
}
and the following instance
{"id": "1234"}
we would expect an error where keyword = format but instead we get
Not sure if this is the right repo but feels like the closest - feel free to move. I haven't investigated this much other than reproducing as it may have something to do with an upstream issue in the validator itself.
Given the following schema
and the following instance
we would expect an error where keyword = format but instead we get
This doesn't seem to happen with other formats (urii / ipv4 / ipv6 / email / hostname / date).
cc @istreeter