# Specify a schema to use when dealing with JSONC files \(\#44250\) · gitcafe/zed

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

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

Visibility: public

Requested revision: a350438a21c80e1199ceae78f4e9f7e6f7403330

Requested commit: a350438a21c80e1199ceae78f4e9f7e6f7403330

Commit: a350438a21c80e1199ceae78f4e9f7e6f7403330

Tree: b2f495726a5fa88df67c2ce0bf1084a8c4ebf3f6

Author: Kirill Bulatov

Committer: GitHub

## Message

```
Specify a schema to use when dealing with JSONC files (#44250)

Follow-up of https://github.com/zed-industries/zed/pull/43854
Closes https://github.com/zed-industries/zed/issues/40970

Seems that json language server does not distinguish between JSONC and
JSON files in runtime, but there is a static schema, which accepts globs
in its `fileMatch` fields.

Use all glob overrides and file suffixes for JSONC inside those match
fields, and provide a grammar for such matches, which accepts trailing
commas.

Release Notes:

- Improved JSONC trailing comma handling
```

## Parents

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

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