Skip to content

Commit e6fe4a5

Browse files
committed
improve wording about JSON Schema in zls.json docs
1 parent 94d6c94 commit e6fe4a5

File tree

1 file changed

+6
-3
lines changed

1 file changed

+6
-3
lines changed

content/zls/configure/zls-json.smd

Lines changed: 6 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -53,7 +53,7 @@ After creating the configuration file at `$local_config_dir/zls.json`, `zls env`
5353

5454
## JSON Schema
5555

56-
ZLS provides a [JSON Schema](https://github.com/zigtools/zls/blob/master/schema.json) to validate the configuration file. It can be used to validate the configuration file and provide IntelliSense features to editors. Further information about JSON Schemas can be found at https://json-schema.org.
56+
ZLS provides a [JSON Schema](https://github.com/zigtools/zls/blob/master/schema.json) for validating the config file and enabling IntelliSense features in editors. Further information about JSON Schemas can be found at https://json-schema.org.
5757

5858
You can add a mapping to `zls.json` that can be used by *some* editors:
5959

@@ -68,5 +68,8 @@ You can add a mapping to `zls.json` that can be used by *some* editors:
6868

6969
Please refer to your Editor's Documentation to find out if and how they support JSON Schemas.
7070

71-
Be aware that configuration options change over time. The example above assumes that you are using ZLS nightly/master. If you use a tagged release of ZLS, you will need to the JSON Schema of the respective version:
72-
`https://raw.githubusercontent.com/zigtools/zls/refs/tags/<ZLS_VERSION_HERE>/schema.json`.
71+
Be aware that configuration options change over time. The example above assumes that you are using ZLS nightly/master. When using a tagged release of ZLS, use the JSON Schema file corresponding to that version, like so:
72+
73+
```
74+
https://raw.githubusercontent.com/zigtools/zls/refs/tags/<ZLS_VERSION_HERE>/schema.json
75+
```

0 commit comments

Comments
 (0)