Skip to content

feat: schema store support - #327628

Closed
Vincent Biret (baywet) wants to merge 3 commits into
microsoft:mainfrom
baywet:feat/schema-store-contributes
Closed

feat: schema store support#327628
Vincent Biret (baywet) wants to merge 3 commits into
microsoft:mainfrom
baywet:feat/schema-store-contributes

Conversation

@baywet

@baywet Vincent Biret (baywet) commented Jul 27, 2026

Copy link
Copy Markdown
Member

Closes #325970

Supersedes #327297.

fixes #26289

Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>
Copilot AI review requested due to automatic review settings July 27, 2026 13:32
@baywet

Copy link
Copy Markdown
Member Author

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Adds SchemaStore catalog support to JSON language features.

Changes:

  • Registers the public SchemaStore catalog.
  • Loads remote registries through the schema request service.
  • Refreshes associations when trust settings change.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 1 comment.

File Description
extensions/json-language-features/package.json Registers the SchemaStore catalog.
extensions/json-language-features/client/src/jsonClient.ts Supports trusted remote registry loading and refreshes.

Comment thread extensions/json-language-features/client/src/jsonClient.ts Outdated

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Copilot reviewed 2 out of 2 changed files in this pull request and generated 2 comments.

Comment on lines +574 to +577
getSchemaAssociations(true, true).then(associations => {
schemaAssociationRefreshIncludesRemoteRegistries = true;
client.sendNotification(SchemaAssociationNotification.type, associations);
});
: await getRegistryContent(registryUri.toString(true));
const registry = <{ schemas?: { url?: string; fileMatch?: string[] }[] }>JSON.parse(rawStr);
if (Array.isArray(registry.schemas)) {
const result: ISchemaAssociation[] = [];
@aeschli

Copy link
Copy Markdown
Contributor

I find it difficult to understand what the PR exactly tries to achieve.

Can we start with an issue that describes the requirements? I'm happy to take it from there and create PRs we don't need to discuss the details on how where what exactly be implemented (in the client, on the server, in the service...)

@baywet

Copy link
Copy Markdown
Member Author

Martin Aeschlimann (@aeschli) sure, I've provided all the details I could think of here #26289 (comment) Let me know if you have any additional comments or questions.

@aeschli

Copy link
Copy Markdown
Contributor

Closing this PR

@baywet

Copy link
Copy Markdown
Member Author

Martin Aeschlimann (@aeschli) are you starting a new pull request to implement that directly? Could you share the link please?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[json] use the schemastore catalog

4 participants