Admins will be upgrading ORNL GitLab Servers on Saturday, 16 May 2026, from 7 AM until 11 AM EST. Repositories will experience intermittent outages during this time.
"description":"Controls whether or not Spectral is enabled.",
"scope":"resource",
"type":"boolean"
},
"spectral.rulesetFile":{
"description":"Location of the ruleset file to use when validating. If omitted, the default is a .spectral.yml/.spectral.json in the same folder as the document being validated. Paths are relative to the workspace. This can also be a remote HTTP url.",
"scope":"resource",
"type":"string"
},
"spectral.run":{
"default":"onType",
"description":"Run the linter on save (onSave) or as you type (onType).",
"enum":[
"onSave",
"onType"
],
"scope":"resource",
"type":"string"
},
"spectral.trace.server":{
"default":"off",
"description":"Traces the communication between VS Code and the language server.",
"enum":[
"off",
"messages",
"verbose"
],
"scope":"window",
"type":"string"
},
"spectral.validateFiles":{
"description":"An array of file globs (e.g., `**/*.yaml`) in minimatch glob format which should be validated by Spectral. If language identifiers are also specified, the file must match both in order to be validated. You can also use negative file globs (e.g., `!**/package.json`) here to exclude files.",
"items":{
"type":"string"
},
"scope":"resource",
"type":"array"
},
"spectral.validateLanguages":{
"default":[
"json",
"yaml"
],
"description":"An array of language IDs which should be validated by Spectral. If file globs are also specified, the file must match both in order to be validated.",
"items":{
"type":"string"
},
"scope":"resource",
"type":"array"
}
},
"title":"Spectral",
"type":"object"
},
"commands":[
{
"title":"Show Output Channel",
"category":"Spectral",
"command":"spectral.showOutputChannel"
}
]
},
"description":"JSON/YAML linter with OpenAPI and custom ruleset support.",
# Instead of the build script that spectral-language-server provides (ref: https://github.com/luizcorreia/spectral-language-server/blob/master/script/vscode-spectral-build.sh), we build vscode-spectral manually.
# This is because the script must go through the network and will not work under the Nix sandbox environment.
# FIXME: vscode-spactral depends on @rollup/pluginutils, but it may have a bug that doesn't provide the type definitions for NodeNext module resolution. (ref: https://github.com/rollup/plugins/issues/1192)
# tsc detects some type errors in the code. However we ignore this because it's not a problem for the final build if server/dist is generated.