Format assertions should be enabled for `optional/ecmascript-regex.json`

[justin-tay]

Describe the bug
Format assertions should be enabled for optional/ecmascript-regex.json as the \\a is not an ECMA 262 control escape test is a format "format": "regex" that expects the result to be invalid.

    {
        "description": "\\a is not an ECMA 262 control escape",
        "schema": {
            "$schema": "https://json-schema.org/draft/2020-12/schema",
            "format": "regex"
        },
        "tests": [
            {
                "description": "when used as a pattern",
                "data": "\\a",
                "valid": false
            }
        ]
    }

https://github.com/json-schema-org/JSON-Schema-Test-Suite/blob/9fc880bfb6d8ccd093bc82431f17d13681ffae8e/tests/draft2020-12/optional/ecmascript-regex.json#L408-L421

Additional context
The current networknt json-schema-validator 1.4.0 doesn't pass the test but an upcoming version will.

[big-andy-coates]

Thanks for letting me know @justin-tay . I'll take a look when I get time, or feel free to raise a PR.

[big-andy-coates]

Hey @justin-tay, I've raised json-schema-org/JSON-Schema-Test-Suite#751 to fix the issue at source.

Let's see what happens with that.

[justin-tay]

There is a related discussion on this specific test

• Move test of \a regex character to optional/format/regex json-schema-org/JSON-Schema-Test-Suite#740

[big-andy-coates]

@justin-tay With json-schema-org/JSON-Schema-Test-Suite#751 merged, I'm assuming this issue is now resolved?

[justin-tay]

Closing as resolved upstream.