[json] allow to override & replace existing schemas

[abgox]

Does this issue occur when all extensions are disabled?: Yes/No

• VS Code Version: 1.90.2
• OS Version: Windows 11 Steps to Reproduce:

1. Add schema in settings.json

   "json.schemas": [
       {
           "fileMatch": [
               "demo.json"
           ],
           "url": "https://abgox.github.io/schema/prettier/zh-CN/.prettierrc-min.json"
       },
       {
           "fileMatch": [
               "demo.json"
           ],
           "url": "https://abgox.github.io/schema/prettier/en-US/.prettierrc-min.json"
       }
   ]

2. When I edit a demo.json, it matches to two schema.
3. But，I cannot select the specified json schema !

4. When I try to apply a given schema, it just goes to the schema page and doesn't apply it!

[abgox]

• When I actually write .prettierrc.json, even though it matches more than one schema, because the prettier plugin is installed, it will only use the json schema provided by the plugin by default.
• I configured some custom architecture, but I can't apply the custom architecture.
• I wish I could apply the selected architecture with a mouse click, or the Enter key, which should also be a correct experience!

[abgox]

• By the way, when I define the schema in settings.json, it means that I want to use my own defined schema, not the default or third-party-provided one.
• So, in this case, the schema I defined in settings.json should have the highest priority. It should take effect immediately, without me even having to make a choice.

[aeschli]

At the moment, schemas are always additive. There's currently not way of disabling other schemas.

[abgox]

• Since it is now additive, it will always use the first added schema.
• Would it be possible to try to add the schema from settings.json first during the addition process?
• As I mentioned above, the user-defined schema should be the first to be loaded.

• By the way, when I define the schema in settings.json, it means that I want to use my own defined schema, not the default or third-party-provided one.
• So, in this case, the schema I defined in settings.json should have the highest priority. It should take effect immediately, without me even having to make a choice.

[abgox]

By the way, all schemas are as follows:

1. The $schema attribute in the JSON file.
2. The json.schemas attribute in settings.json (Workspace)
3. The json.schemas attribute in settings.json (User)
4. The schema provided by the extension.

---

• I believe the correct priority for schema should be: 1 > 2 > 3 > 4

• But Now, It's 1 > 4 > 3 > 2

---

At the moment, schemas are always additive. There's currently not way of disabling other schemas.

• @aeschli
• It doesn't need to disable the other schemas, it just needs to accumulate them with the correct priority when it comes time to accumulate them.

[aeschli]

All matching schemas are combined with an allOf. The schema is tested against all schemas. So the order does not matter.

Note that schemas defined in the workspace settings replace the schemas in the user settings. This is how the VS Code settings work.

[abgox]

• I set up a different schema in the user settings and workspace settings to test, but it's not replaced.
• Also, it was the schema in the user settings that took effect, not the workspace settings.

Note that schemas defined in the workspace settings replace the schemas in the user settings.