Replies: 3 comments 3 replies
-
|
Hii lonix1, Yes, the CLI already defines defaults. You dont need to specify The base defaults are shared with the VS Code extension via the same core library, so they are largely the same (except the editor specific paths like .vscode and .vscode-insiders which only make sense in the extension context). To see the exact defaults for your specific version, check the DefaultSettings.ts file directly. That is the source of truth for both CLI and extension. If you want to add custom ignorePaths, add them to cspell.json in your project root: {
"ignorePaths": [
"dist",
"coverage"
]
}Both the CLI and VS Code extension will pick this up and merge it on top of the defaults so you don't need to re list the defaults. |
Beta Was this translation helpful? Give feedback.
-
|
@Jason3S Maybe cspell/packages/cspell/src/util/glob.ts Line 26 in 492ee87 should be const defaultExcludeGlobs = [
'.git/',
'node_modules/',
'package-lock.json',
'pnpm-lock.yaml',
];? |
Beta Was this translation helpful? Give feedback.
-
|
Moved to issue #8937 |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
For the vscode extension:
We can easily tell which paths are ignored by default, by looking at the default JSON settings:
For the cli tool:
I can't determine what to use for
ignorePaths? Does the cli already define defaults, or am I supposed to do so?Beta Was this translation helpful? Give feedback.
All reactions