Expose JSON worker

[mevisioam]

This PR fixes #727 and addresses review comments (I think so) from an original PR #3956 which became stale for some reason.

I just want to get things JSON worker faster to Monaco, because it's needed for my project.

My use case is to provide insights to the end user after analyzing JSON schemas of the edited document. Plus, include the motivation from an original PR:

Exposes the JSON worker and the parseDocument function from the JSON Worker.

This is useful when editors want to use the JSON Worker's ability to parse the document, as using a separate parser can result in inconsistencies and does double the work.

[mevisioam]

@microsoft-github-policy-service agree

[mevisioam]

@hediet @aeschli can you take a look? Since you looked at #3956 previously :)

[aeschli]

The types that are used from jsonService should be copied to json/monaco.contribution.ts so that the d.ts file is self-contained.

[mevisioam]

Got it, lemme fix it.

[mevisioam]

Though, I wonder then why we have pretty much the same setup in https://github.com/microsoft/monaco-editor/blob/main/src/language/typescript/monaco.contribution.ts#L6 :)

[mevisioam]

Ah, sorry, it's jsonMode not jsonService.

[mevisioam]

@aeschli looks crazy, but I'm done, sir :)

[aeschli]

Yes, that's a lot of types, I don't like it either. Especially as these types duplicate some of the Monaco types (e.g. IPosition, IRange), but Monaco types 1 based (the first column and line is 1, not 0), while the LSP types are 0 based.

Not sure what approach to choose:

• Keep the API minimal. What API from the worker do you really need?
• In typesscript/monaco.contribution.ts the APis just return any. We could do that.

@alexdima What do yo think?

[mevisioam]

@aeschli:

• Keep the API minimal. What API from the worker do you really need?

Think, I could leave it to only getMatchingSchemas and parseDocument as in the initial PR did, afair.

[mevisioam]

@aeschli cleaned up a lil bit

[mevisioam]

@aeschli @alexdima this state shud be fine now.

[aeschli]

Looks good!

[mevisioam]

@aeschli thx for the review, when shall this end up in npm install monaco-editor? :)

[aeschli]

I think @hediet makes a Monaco editor release in the same week VS Code is released. So this should be in the last week of January.