Fixed error when no schema matches.
Additionally export some members for jsonDocument.
They are also needed to easily extend functionality.

@ianchi I'm very hesitant to make getMatchingSchemas API in the current form.
Can you provide some use cases?

Hi @aeschi,

I have a schema that has a custom keyword that triggers a custom validation logic.
I need to do this validation on the input files and report errors on a cli tool and also I made an extension that adds the errors as diagnostics to VSCode.

Having the matching schemas makes all this dead simple.
Without that I would have to rewrite all the schema validation logic, as there is no extension mechanism.

This can be validated with custom keywords using Ajv, but it is really not useful for reporting document position of the error.

I understand that it exposes some implementation details, but it allows to use it to easily extend functionality.
Alternatively some hook could be implemented to call custom functions, but I understood from some other Issue, that you weren’t willing to do so.

Exposing some of jsonDocument functionality also allows me to easily add some custom hover info with the vscode extension, that is dependant on the schema of the cursor’s node

Hi @aeschli, any chance of considering this?

Or any other approach to leverage this service and be able to extend it to use it on custom validations an hoover info?

All CLA requirements met.

Hi @ianchi , I pushed a commit that hides the inverted schema. Also I polished the code and added tests.

If you can sign the CLA, then I can push the change.

Hi @aeschli,
Just signed the CLA.
Great to see this merged.

Thanks!