replace json theia extension with vscode one

[akosyakov]

What it does

Fixes: #7981
Fixes: #3983

• fix 7981, fix 3983: replace json theia extension with vscode one
• document breaking changes
• deprecate contributing language support from Theia extension

Please see CHANGELOG for breaking changes.

How to test

• verify that smartness available in settings (user, workspace), debug and task files as before
• verify that user data as settings and keymaps are preserved
• verify that jsonValidation contribution point from VS Code extension is respected
• verify How to test from Support relative paths for JSON schema associations (Fix #7140) #7225

Review checklist

• as an author, I have thoroughly tested my changes and carefully followed the review guidelines

Reminder for reviewers

• as a reviewer, I agree to behave in accordance with the review guidelines

[vince-fugnitto]

I noticed a difference when editing preferences in .theia vs .vscode.
When editing .vscode/settings.json I have more autocompletion or intelligence available, however for both I do not see the list of preferences I can update (compared to vscode).

theia:

vscode:

[akosyakov]

@vince-fugnitto How do you reproduce it. I've just tried latest state in Gitpod:

Could you check terminal that VS Code extensions are downloaded successfully for you?

[vince-fugnitto]

@vince-fugnitto How do you reproduce it. I've just tried latest state in Gitpod:

I re-verified and it works correctly now, I'm not sure how I got in that weird state before.

[akosyakov]

It is required for #7100

@vince-fugnitto Could you have a look again please? Is there anything else should be addressed?

[vince-fugnitto]

@akosyakov I verified the changes and they work well. I've verified that:

• settings.json: both theia and vscode preferences has problem marker support and autocompletion
• launch.json: both theia and vscode debug has problem marker support and autocompletion
• keymaps.json: the entries are correctly populated like before, and the updates are applied correctly

I also looked over the code and did not see anything that looked incorrect.

[bd82]

Hello @akosyakov

What is the behavior when multiple jsonSchemas are registered for an identical fileMatch pattern?
For example: If there is a schemaStore registration for xyz.json files and also a VSCode Ext with jsonContribution forh xyz.json?

Basically do jsonContribution replace schemaStore registrations or are they added as extra schemas?

[akosyakov]

Basically do jsonContribution replace schemaStore registrations or are they added as extra schemas?

They are added as extra schemas. You will need to check how json-language-featuers built-in extension handles it.

[akosyakov]

I'm updating deprecation notes with a link to VS Code docs about how to integrate a language server via VS Code extension and merging if there are no objections.

[azatsarynnyy]

I've tested it in the context of Tasks functionality.