You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The original idea, was the local config has more knowledge of the files being checked than a global config.
This allows for things like specifying the language.
For example:
cspell.config.yaml - language: en
i18n/de/cspell.config.yaml - language: de
i18n/de/README.md
At the root:
cspell "**/*.md", would use German when spellchecking i18n/de/README.md.
But by automatically turning on noConfigSearch, the following would break:
cspell --config cspell.config.yaml "**/*.md" would use English instead of German.
Even though both invocations of cspell use cspell.config.yaml, the behavior would be different.
I propose added two new options: --no-config-search and --config-root.
--no-config-search would just enabled adding the behavior to the command line.
--stop-config-search-at <dir> would tell the spellchecker to not look further up the hierarchy than the specified <dir>. It also makes sense that more than one stop could be wanted.
The original idea, was the local config has more knowledge of the files being checked than a global config.
This allows for things like specifying the language.
For example:
At the root:
cspell "**/*.md"
, would use German when spellcheckingi18n/de/README.md
.But by automatically turning on
noConfigSearch
, the following would break:cspell --config cspell.config.yaml "**/*.md"
would use English instead of German.Even though both invocations of
cspell
usecspell.config.yaml
, the behavior would be different.I propose added two new options:
--no-config-search
and--config-root
.--no-config-search
would just enabled adding the behavior to the command line.--stop-config-search-at <dir>
would tell the spellchecker to not look further up the hierarchy than the specified<dir>
. It also makes sense that more than one stop could be wanted.Originally posted by @Jason3S in #4750 (comment)
The text was updated successfully, but these errors were encountered: