[MohitSAGAR11]

Closes #294

Summary

A schema that uses a keyword the package doesn't know about makes jsonSchemaErrors throw Encountered unsupported keyword .... This adds support for the keywords the standard dialects and the OpenAPI dialects can put in the AST.

Content keywords (draft-07 and up)

contentMediaType, contentEncoding, and contentSchema are annotation-only, but they weren't registered. They're now registered as annotations, alongside comment, default, description, and examples.

OpenAPI keywords

The OpenAPI dialects define their own keyword URIs:

• The annotation-only keywords discriminator, example, externalDocs, xml, and nullable (OpenAPI 3.0) don't affect validation and are registered as annotations.
• The OpenAPI 3.0 type keyword asserts types like the standard type keyword, so the type/const/enum error handler now recognizes it and produces the same messages (including the null type added by nullable).

OpenAPI 3.1 and 3.2 reuse the same keyword URIs, so they're covered too.

Tests

• src/test-suite/tests/content.json — the content keywords are annotations across draft-07, 2019-09, and 2020-12.
• src/openapi.test.js — OpenAPI 3.0/3.1/3.2 type assertions, nullable, annotation keywords, and annotation-only schemas.

npm test (1338 passing), npm run lint, and npm run type-check all pass.

[MohitSAGAR11]

Hi @jdesrosiers, thanks again for the quick reply on #294.

While this PR is up, I wanted to check in: is there anything you'd like help with, or a direction you'd prefer I work toward? I'm happy to keep doing what I've been doing — finding and reporting issues, then opening a PR for the ones you approve — but I didn't want to assume. Let me know what would be most useful.

[jdesrosiers]

Look good so far. Please move openapi.test.js to use the JSON-based test suite.

[MohitSAGAR11]

Thanks! I moved the OpenAPI tests to the JSON test suite and removed openapi.test.js.

• OpenAPI 3.1 and 3.2 now run the whole tests suite. They all pass as-is since both dialects are based on 2020-12.
• OpenAPI 3.0 only supports a subset of the keywords, so the OpenAPI-specific tests are in a new src/test-suite/openapi/ folder that runs against all three OpenAPI dialects. compatibility there uses 30, 31, and 32, for example "=30" for nullable. I added a short section about it to the test-suite README.

I also rebased on main. If you'd prefer the OpenAPI tests organized differently, let me know and I'll change it.

[MohitSAGAR11]

@jdesrosiers just a gentle ping on this one. I moved the OpenAPI tests into the JSON test suite like you asked. Let me know if you'd like anything changed.

[jdesrosiers]

I ended up going a slightly different direction. I changed it to make the OpenAPI 3.0 type keyword an alias of type, so every error handler sees it, not just type/const/enum. The way it was, anyOf and oneOf didn't drop alternatives of the wrong type under 3.0.

[MohitSAGAR11]

Thanks for merging, and for the fixes! Making it an alias of type is much cleaner. I only handled it in the type/const/enum handler and missed that anyOf/oneOf use the type to drop alternatives. Running the main suite against 3.0 also checks that every handler sees it. Next time a dialect redefines a standard keyword, I'll alias it instead of special-casing handlers.