[Feature Request] Draft 2020-12 support for schema definitions

[AE1NS]

Context

• This issue is not a bug report. (please use a different template for reporting a bug)
• This issue is not a duplicate of an existing issue. (please use the search to find existing issues)

Description

Are you going to support the the Draft 2020-12 version for schema definitions in the future? When I set $schema: 'https://json-schema.org/draft/2020-12/schema', inside my schema objects, I get this output in my monaco editor: Draft 2020-12 schemas are not yet fully supported.(768).

With the new draft https://json-schema.org/draft/2020-12/release-notes.html we could i.e. use the unevaluatedProperties feature.

In my case, I could solve the issue described here: https://stackoverflow.com/questions/64143406/allow-additional-properties-in-reference-schemas-but-none-else

[mjperrone]

I would be interested in this support

[elitemike]

I could use this as well. My JSON that meets the 2020-12 spec starts with an array and the error shows on the open bracket. No other errors show further down. I do get auto complete suggestions from my schema in the hierarchy, but no errors about missing required keys.

[elitemike]

Has there been any movement on this? I'm trying to put in a work around for my users and it's not very clean.