# JSON Schema URIs \(\#38916\) · gitcafe/zed

[View on GitCafe](https://git.cafe/gitcafe/zed/commit/4aac5642c13faabf2a2d6bd765ff95fbf55259ab)

Repository: [gitcafe/zed](https://git.cafe/gitcafe/zed)

Visibility: public

Requested revision: 4aac5642c13faabf2a2d6bd765ff95fbf55259ab

Requested commit: 4aac5642c13faabf2a2d6bd765ff95fbf55259ab

Commit: 4aac5642c13faabf2a2d6bd765ff95fbf55259ab

Tree: 9b386fb697d99d961e57603a4c208ae218a5bc4f

Author: Ben Kunkle

Committer: GitHub

## Message

```
JSON Schema URIs (#38916)

Closes #ISSUE

Improves the efficiency of our interactions with the Zed language
server. Previously, on startup and after every workspace configuration
changed notification, we would send >1MB of JSON Schemas to the JSON
LSP. The only reason this had to happen was due to the case where an
extension was installed that would result in a change to the JSON schema
for settings (i.e. added language, theme, etc).

This PR changes the behavior to use the URI LSP extensions of
`vscode-json-language-server` in order to send the server URI's that it
can then use to fetch the schemas as needed (i.e. the settings schema is
only generated and sent when `settings.json` is opened. This brings the
JSON we send to on startup and after every workspace configuration
changed notification down to a couple of KB.

Additionally, using another LSP extension request we can notify the
server when a schema has changed using the URI as a key, so we no longer
have to send a workspace configuration changed notification, and the
schema contents will only be re-requested and regenerated if the schema
is in use.

Release Notes:

- Improved the efficiency of communication with the builtin JSON LSP.
JSON Schemas are no longer sent to the JSON language server in their
full form. If you wish to view a builtin JSON schema in the language
server info tab of the language server logs (`dev: open language server
logs`), you must now use the `editor: open url` action with your cursor
over the URL that is sent to the server.
- Made it so that Zed urls (`zed://...`) are resolved locally when
opened within the editor instead of being resolved through the OS. Users
who could not previously open `zed://*` URLs in the editor can now do so
by pasting the link into a buffer and using the `editor: open url`
action (please open an issue if this is the case for you!).

---------

Co-authored-by: Michael <michael@zed.dev>
```

## Parents

- [30b49cfbf5f56c8700a958acdbb2afe4e910a767](https://git.cafe/gitcafe/zed/commit/30b49cfbf5f56c8700a958acdbb2afe4e910a767?format=markdown)

[Source at this commit](https://git.cafe/gitcafe/zed/tree/4aac5642c13faabf2a2d6bd765ff95fbf55259ab?format=markdown)