yaml-language-server 1.12.1-9d71bbf.0 → 1.12.1-a8c9883.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +13 -0
- package/eslint-result.sarif +40 -558
- package/lib/esm/languageserver/handlers/validationHandlers.js.map +1 -1
- package/lib/esm/languageservice/parser/jsonParser07.d.ts +8 -0
- package/lib/esm/languageservice/parser/jsonParser07.js +11 -1
- package/lib/esm/languageservice/parser/jsonParser07.js.map +1 -1
- package/lib/esm/languageservice/services/validation/unused-anchors.js +4 -2
- package/lib/esm/languageservice/services/validation/unused-anchors.js.map +1 -1
- package/lib/esm/languageservice/services/yamlHover.d.ts +1 -0
- package/lib/esm/languageservice/services/yamlHover.js +5 -3
- package/lib/esm/languageservice/services/yamlHover.js.map +1 -1
- package/lib/esm/languageservice/utils/arrUtils.d.ts +1 -1
- package/lib/esm/languageservice/utils/arrUtils.js +0 -1
- package/lib/esm/languageservice/utils/arrUtils.js.map +1 -1
- package/lib/esm/requestTypes.d.ts +10 -10
- package/lib/esm/requestTypes.js +0 -2
- package/lib/esm/requestTypes.js.map +1 -1
- package/lib/esm/webworker/yamlServerMain.js +0 -2
- package/lib/esm/webworker/yamlServerMain.js.map +1 -1
- package/lib/umd/languageserver/handlers/validationHandlers.js.map +1 -1
- package/lib/umd/languageservice/parser/jsonParser07.d.ts +8 -0
- package/lib/umd/languageservice/parser/jsonParser07.js +11 -1
- package/lib/umd/languageservice/parser/jsonParser07.js.map +1 -1
- package/lib/umd/languageservice/services/validation/unused-anchors.js +4 -2
- package/lib/umd/languageservice/services/validation/unused-anchors.js.map +1 -1
- package/lib/umd/languageservice/services/yamlHover.d.ts +1 -0
- package/lib/umd/languageservice/services/yamlHover.js +4 -2
- package/lib/umd/languageservice/services/yamlHover.js.map +1 -1
- package/lib/umd/languageservice/utils/arrUtils.d.ts +1 -1
- package/lib/umd/languageservice/utils/arrUtils.js +0 -1
- package/lib/umd/languageservice/utils/arrUtils.js.map +1 -1
- package/lib/umd/requestTypes.d.ts +10 -10
- package/lib/umd/requestTypes.js +0 -2
- package/lib/umd/requestTypes.js.map +1 -1
- package/lib/umd/webworker/yamlServerMain.js +0 -2
- package/lib/umd/webworker/yamlServerMain.js.map +1 -1
- package/out/server/src/languageserver/handlers/validationHandlers.js.map +1 -1
- package/out/server/src/languageservice/parser/jsonParser07.d.ts +8 -0
- package/out/server/src/languageservice/parser/jsonParser07.js +11 -1
- package/out/server/src/languageservice/parser/jsonParser07.js.map +1 -1
- package/out/server/src/languageservice/services/validation/unused-anchors.js +4 -2
- package/out/server/src/languageservice/services/validation/unused-anchors.js.map +1 -1
- package/out/server/src/languageservice/services/yamlHover.d.ts +1 -0
- package/out/server/src/languageservice/services/yamlHover.js +4 -2
- package/out/server/src/languageservice/services/yamlHover.js.map +1 -1
- package/out/server/src/languageservice/utils/arrUtils.d.ts +1 -1
- package/out/server/src/languageservice/utils/arrUtils.js +0 -1
- package/out/server/src/languageservice/utils/arrUtils.js.map +1 -1
- package/out/server/src/requestTypes.d.ts +10 -10
- package/out/server/src/requestTypes.js +0 -2
- package/out/server/src/requestTypes.js.map +1 -1
- package/out/server/src/webworker/yamlServerMain.js +0 -2
- package/out/server/src/webworker/yamlServerMain.js.map +1 -1
- package/out/server/test/hover.test.js +21 -1
- package/out/server/test/hover.test.js.map +1 -1
- package/out/server/test/integration.test.js +3 -2
- package/out/server/test/integration.test.js.map +1 -1
- package/out/server/test/multipleDocuments.test.js +1 -0
- package/out/server/test/multipleDocuments.test.js.map +1 -1
- package/out/server/test/schemaValidation.test.js +60 -0
- package/out/server/test/schemaValidation.test.js.map +1 -1
- package/out/server/test/yamlValidation.test.js +3 -2
- package/out/server/test/yamlValidation.test.js.map +1 -1
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -225,6 +225,19 @@ yaml.schemas: {
|
|
|
225
225
|
|
|
226
226
|
`yaml.schemas` allows you to specify json schemas that you want to validate against the yaml that you write. Kubernetes is an optional field. It does not require a url as the language server will provide that. You just need the keyword kubernetes and a glob pattern.
|
|
227
227
|
|
|
228
|
+
### Nested Schema References
|
|
229
|
+
|
|
230
|
+
Suppose a file is meant to be a component of an existing schema (like a `job.yaml` file in a circleci orb), but there isn't a standalone schema that you can reference. If there is a nested schema definition for this subcomponent, you can reference it using a url fragment, e.g.:
|
|
231
|
+
|
|
232
|
+
```
|
|
233
|
+
yaml.schemas: {
|
|
234
|
+
"https://json.schemastore.org/circleciconfig#/definitions/jobs/additionalProperties": "/src/jobs/*.yaml",
|
|
235
|
+
}
|
|
236
|
+
```
|
|
237
|
+
|
|
238
|
+
> **Note**
|
|
239
|
+
> This will require reading your existing schema and understanding the schemastore structure a bit. (TODO: link to a documentation or blog post here?)
|
|
240
|
+
|
|
228
241
|
### Using inlined schema
|
|
229
242
|
|
|
230
243
|
It is possible to specify a yaml schema using a modeline.
|