Repository navigation
Expand file tree
/
Copy pathpackage.nls.json
More file actions
48 lines (48 loc) · 8 KB
/
Copy pathpackage.nls.json
File metadata and controls
48 lines (48 loc) · 8 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
{
"displayName": "ShellCheck",
"description": "Integrates ShellCheck into VS Code, a linter for Shell scripts.",
"command.runLint.title": "Lint Current Document",
"command.collectDiagnostics.title": "Collect Diagnostics For Current Document",
"command.showMenu.title": "Show Menu",
"command.useWasmRuntime.title": "Use the Experimental WebAssembly Runtime",
"icon.shellcheck-logo.description": "ShellCheck logo",
"config.title": "ShellCheck",
"config.configFiles.title": "Config Files",
"config.nativeRuntime.title": "Native Runtime",
"config.enable.description": "Whether ShellCheck is enabled or not.",
"config.enableQuickFix.markdownDescription": "Whether to enable the _Quick Fix_ feature or not.",
"config.markdownDiagnostics.markdownDescription": "**Experimental:** Show a formatted ShellCheck hover with severity and rule documentation. VS Code also displays the original diagnostic; the Problems view is unchanged. [Read the documentation](https://github.com/vscode-shellcheck/vscode-shellcheck#shellcheckmarkdowndiagnostics).",
"config.executablePath.markdownDescription": "Path to the `shellcheck` executable (bundled binaries will be used if empty). Only used when `#shellcheck.runtime#` is `native`, so it has no effect in VS Code for the Web.",
"config.runtime.markdownDescription": "**Experimental.** Which ShellCheck runtime to use. VS Code for the Web always uses `wasm` and ignores this setting.\n\n- `auto` — `native` on desktop and `wasm` in VS Code for the Web. This is the default.\n- `native` — run the bundled or user-provided `shellcheck` executable. This is the only supported runtime on desktop.\n- `wasm` — run a bundled WebAssembly (WASI) build of ShellCheck inside the editor. No executable is required and it works on every platform and in virtual workspaces, but linting is currently 3-4x slower than native, `#shellcheck.executablePath#` is ignored, and files outside the document's workspace folder are not visible to `source` directives or `.shellcheckrc` lookup.",
"config.runtime.enumDescriptions.0": "Run the shellcheck executable on desktop and WebAssembly in VS Code for the Web.",
"config.runtime.enumDescriptions.1": "Run the bundled or user-provided shellcheck executable.",
"config.runtime.enumDescriptions.2": "Run the bundled WebAssembly build of ShellCheck (experimental, slower).",
"config.run.description": "What triggers a lint: typing, saving, or only the Lint Current Document command.",
"config.exclude.markdownDescription": "Exclude certain error codes. For example, to exclude [SC1017](https://shellcheck.net/wiki/SC1017), enter _1017_. Enumerated error codes can be found [in this gist](https://gist.github.com/nicerobot/53cee11ee0abbdc997661e65b348f375). Always prefer to use a `.shellcheckrc` file instead of this setting.",
"config.exclude.items.patternErrorMessage": "Valid shellcheck error code should be 4-digit numbers, 1017 for example.\n",
"config.customArgs.markdownDescription": "Custom arguments to pass to ShellCheck. Always prefer to use a `.shellcheckrc` file instead of this setting. When `#shellcheck.runtime#` is `wasm`, as it always is in VS Code for the Web, paths on your machine in these arguments do not resolve.",
"config.ignorePatterns.markdownDescription": "Configure glob patterns for excluding files and folders by ShellCheck. Glob patterns are interpreted relative to the workspace's root folder and use [picomatch](https://github.com/micromatch/picomatch#readme) syntax, which also supports extglob patterns such as `!(*.*)`.",
"config.ignorePatterns.additionalProperties.description": "The glob pattern to match file paths against. Set to true or false to enable or disable the pattern.",
"config.ignoreFileSchemes.description": "Matching file schemes are being ignored by shellcheck. The default also covers the virtual documents of the GitHub Pull Requests extension.",
"config.useWorkspaceRootAsCwd.markdownDescription": "Whether to use the workspace root directory as the current working directory when launching `shellcheck`. Otherwise, the directory of the file being linted will be used.",
"config.runTimeout.markdownDescription": "Seconds a `shellcheck` run may take before it is stopped. `0` uses the default, 30 seconds. A stopped run leaves the document's problems as they were. Only runs started after a change are stopped: a document whose run already hangs is linted again once it is closed and reopened.",
"config.maxConcurrentRuns.markdownDescription": "The most `shellcheck` runs at once. `0` uses the runtime's default: no limit for `native`, 2 for `wasm`. Lints beyond it wait for a running one to finish. Each `wasm` run takes a worker of its own, which can use over 100 MiB of memory.",
"config.logLevel.description": "The trace level the extension logs at, defaults to 'info'.",
"config.disableVersionCheck.markdownDescription": "Whether to disable shellcheck binary version check, which prompts for updating when an outdated version is found. The check only runs when `#shellcheck.runtime#` is `native`, so it has no effect in VS Code for the Web.",
"config.watchConfigFiles.workspace.markdownDescription": "Lint open documents again when a `.shellcheckrc` or `shellcheckrc` in the workspace is created, changed or deleted, along with a file passed with `--rcfile` in `#shellcheck.customArgs#` that lives in the workspace. Only the documents that can pick up the changed file are linted again, and never those passed `--norc`.",
"config.watchConfigFiles.user.markdownDescription": "Lint open documents again when a ShellCheck config file outside the workspace is created, changed or deleted: a `.shellcheckrc` or `shellcheckrc` in a folder above a workspace folder, `~/.shellcheckrc` and `$XDG_CONFIG_HOME/shellcheckrc` (`%APPDATA%\\shellcheckrc` on Windows), and a file passed with `--rcfile` in `#shellcheck.customArgs#` that lives outside the workspace. Only used when `#shellcheck.runtime#` is `native`, the only runtime that can read these files, so it has no effect in VS Code for the Web.",
"walkthrough.whatsNew.title": "What's New in ShellCheck",
"walkthrough.whatsNew.description": "A status bar menu, VS Code for the Web, and more.",
"walkthrough.whatsNew.step.statusBar.title": "ShellCheck in the status bar",
"walkthrough.whatsNew.step.statusBar.description": "Click the ShellCheck icon on the right of the status bar to lint the current document, change when ShellCheck runs, or turn it off for this workspace.",
"walkthrough.whatsNew.step.statusBar.altText": "Clicking the ShellCheck icon in the status bar opens its menu.",
"walkthrough.whatsNew.step.web.title": "VS Code for the Web",
"walkthrough.whatsNew.step.web.description": "ShellCheck now checks your scripts on [vscode.dev](https://vscode.dev) and [github.dev](https://github.dev), with nothing to install.",
"walkthrough.whatsNew.step.web.altText": "ShellCheck reports a problem while typing in VS Code for the Web.",
"walkthrough.whatsNew.step.wasm.title": "A bundled WebAssembly build",
"walkthrough.whatsNew.step.wasm.description": "The extension now bundles a WebAssembly build of ShellCheck. It runs on every platform with no shellcheck binary to install, stays sandboxed to your workspace files, and powers ShellCheck on the web.\n[Try the WebAssembly Runtime](command:shellcheck.useWasmRuntime)",
"walkthrough.whatsNew.step.wasm.altText": "The bundled WebAssembly build runs on every platform, in a sandbox, and on the web.",
"walkthrough.whatsNew.step.configFiles.title": "Lint again when .shellcheckrc changes",
"walkthrough.whatsNew.step.configFiles.description": "ShellCheck can lint your open scripts again as soon as a .shellcheckrc changes, so new rules apply without reopening files. Turn on shellcheck.watchConfigFiles.workspace for config files in your workspace, and shellcheck.watchConfigFiles.user for ones outside it, such as ~/.shellcheckrc. Both are off by default.\n[Open Config File Settings](command:workbench.action.openSettings?%5B%22shellcheck.watchConfigFiles%22%5D)",
"walkthrough.whatsNew.step.configFiles.altText": "Changing .shellcheckrc lints the open scripts again."
}