.cspellrc configuration file
See original GitHub issueIs there a possibility to add .cspellrc
as a valid configuration file?
I don’t want to call --config .cspellrc>
always.
Rather, consider .cspellrc
to be an official configuration file.
Issue Analytics
- State:
- Created a year ago
- Comments:7 (3 by maintainers)
Top Results From Across the Web
Configuration | CSpell
CSpell's behavior can be controlled through a config file. By default it looks for any of the following files: ... Or you can...
Read more >cspell/README.md at main - GitHub
cspell's behavior can be controlled through a config file. By default it looks for any of the following files: ... Or you can...
Read more >Configuration Settings | Spell Checker - Street Side Software
Configuration Settings. Code Spell Checker; Languages and Dictionaries; Reporting and Display; Files, Folders, and Workspaces; Performance; CSpell; Advanced ...
Read more >cspell - npm
A Spelling Checker for Code!. Latest version: 6.18.0, last published: 6 days ago. Start using cspell in your project by running `npm i ......
Read more >CSpell
The default configuration file is ${CSPELL_DIR}/data/Config/cSpell.properties. The variables used in the configuration file are the empirical best value and ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@carlocorradini,
Thank you for the suggestion. There is nothing “standard” about
rc
files. Even the format is not clear. Should it be JSON, or Yaml, or some other format?Historically,
rc
(run command or run config) files tend to be different than the configuration files. They allow you to set defaults for the command line options, instead of the general configuration. Even Babel makes a distinction.A perfect example of an option that would be in the
rc
and not in the configuration is thecache
. This is because it is specific to thecspell
cli and does not apply to the@cspell/eslint-plugin
or to the VS Code spell checker extension. I debated on creating anrc
to take care of that case, but because of the possible confusion, it was decided not to use one.Kind regards, Jason
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.