Support for json-schema > draft-7

[mitodrummer]

Summary

Hello, I am wondering if there is a plan to update to the newest json schema (2020-12 at the time of this ticket). I am needing features from 2019 schema.

TY

[mitodrummer]

microsoft/vscode-json-languageservice#133

Looks like maybe version 4.2.1 of json-languageservice should have it :)

[remcohaszing]

FYI #637 explains why the version is locked. That issue includes a number of related references.

As the reporter of that issue I would totally understand if the version is unlocked in order to support newer JSON schema features.

[gorkem]

@remcohaszing I think we will have to move to a later vscode-json-languageservice not only to get schema support for more recent schema versions but also for issues like #823 are also fixed by later versions.

[remcohaszing]

I suggest to wait for SchemaStore/schemastore#2858.

[gorkem]

No problem. Unfortunately, there are breaking changes on vscode-language-service that we need to adjust yaml-language-server for.

[amimas]

Any update available for this?

[apupier]

microsoft/vscode-json-languageservice#133

Looks like maybe version 4.2.1 of json-languageservice should have it :)

Unfortunately, it seems that it is not workign as expected, this issue is linked from the pointed issue microsoft/vscode#98724

[remcohaszing]

I don’t know what’s the hold up for SchemaStore/schemastore#2858, but it’s taking a long time. It only affects 3 schemas, of which I manage 1, so I can create a workaround for that.

I think it’s best to just update. This will break for a couple of users, but benefit the majority.

[michaeltlombardi]

Updating would be very helpful, as there's a good number of useful keywords in 2019-09 that work even without full support for dynamic references/anchors/vocabulary - notably, the unevaluated* and dependent* keywords for schema composition/extension/conditional validation.

[Cerebus]

Updating is a must, b/c I've got schemas I'd like to use that are on draft 2019-09 and 2020-12. It's a royal PITA when completion is busted for half my stuff b/c yamlls won't grok the schema.

[baywet]

@datho7561 could you please articulate in broad strokes where the changes need to be made for this? Sort of an introduction to the code base + considerations to keep in mind.
From reading this thread, I'm under the impression that this has a dependency on the JSON language server, but the upgrade has been kept behind for some reason, do you have specifics as to why?