struggling to invalid result for vercel/schema.json when doing mutation testing

[awalterschulze]

Similar to issue #874
Blaze does not invalidate this schema correctly

There are other schemas where Blaze does well, but this one only Blaze fails to invalidate:

The schema is vercel/schema.json

mutated invalid

{"buildCommand":"","installCommand":"","outputDirectory":"build","routes":[{"F3d13Na6hA9ThzE63y5L5yTjqT4GF202c":"filesystem","handle":"filesystem"},{"dest":"/shimmer/404.html","src":"/shimmer/(.*)","status":404},{"dest":"/next/404.html","src":"/next/(.*)","status":404},{"dest":"/404.html","src":"/(.*)","status":404}]}

The original valid

{"routes": [{"handle": "filesystem"}, {"src": "/shimmer/(.*)", "status": 404, "dest": "/shimmer/404.html"}, {"src": "/next/(.*)", "status": 404, "dest": "/next/404.html"}, {"src": "/(.*)", "status": 404, "dest": "/404.html"}], "outputDirectory": "build", "installCommand": "", "buildCommand": ""}

[awalterschulze]

The handle fieldname was changed to F3d13Na6hA9ThzE63y5L5yTjqT4GF202c

But handle seems to be a required field, if there is no src field

"routes": ...
    "items": {
        "anyOf": [
          {
            "type": "object",
            "required": [
              "src"
            ],
            ...
          },
           ...
          {
            "type": "object",
            "required": [
              "handle"
            ],
            "additionalProperties": false,
            "properties": {
              "handle": {
...
}

[jviotti]

Another good one, thanks a lot! An over aggressive optimisation. Thanks for surfacing it. Excited to see if your fuzzing reveals anything else. We probably want to eventually upstream these cases to the JSON Schema official test suite, as they are real coverage gaps I guess

[awalterschulze]

My pleasure, thanks for fixing them so quickly and taking them so seriously.

Feel free to take them to the test suite, that is a great idea

[awalterschulze]

I finally did an updated run and I can confirm this issue is fixed