Skip to content

Commit a0de300

Browse files
authored
(docs) explain missing option
And why it's bad to run checks only on changed files
1 parent aa1883f commit a0de300

File tree

1 file changed

+6
-0
lines changed

1 file changed

+6
-0
lines changed

packages/svelte-check/README.md

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -62,6 +62,12 @@ Usage:
6262
| `--diagnostic-sources <js,svelte,css>` | A list of diagnostic sources which should run diagnostics on your code. Possible values are `js` (includes TS), `svelte`, `css`. Comma-separated, inside quotes. By default all are active. Example: `--diagnostic-sources "js,svelte"` |
6363
| `--threshold <error\|warning>` | Filters the diagnostics to display. `error` will output only errors while `warning` will output warnings and errors. |
6464

65+
### FAQ
66+
67+
#### Why is there no option to only check specific files (for example only staged files)?
68+
69+
`svelte-check` needs to know the whole project to do valid checks. Imagine you alter a component property `export let foo` to `export let bar`, but you don't update any of the component usages. They all have errors now but you would not catch them if you only run checks on changed files.
70+
6571
### More docs, preprocessor setup and troubleshooting
6672

6773
[See here](/docs/README.md).

0 commit comments

Comments
 (0)