-
-
Notifications
You must be signed in to change notification settings - Fork 92
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
option to specify includePaths for files #571
Labels
Comments
I think this is a good idea. I'm thinking about the right way to do it.
The setting controls the behavior of the cspell cli and not the cspell library. |
Jason3S
added a commit
that referenced
this issue
Feb 13, 2021
Jason3S
added a commit
that referenced
this issue
Feb 15, 2021
Related to #571 ## Specify `files` Make it possible to specify which files to check in the configuration file. A new configuration field `files` has be added: ```js { // tell cspell to check all JavaScript and Markdown files. files: ["**/*.js", "**/*.md"] } ``` ## Commits * feat: Be able to specify files to spell check within the config. * dev: Use files from config in cli application * dev: add methods to support glob normalization to a common root. * refactor: move the methods to a more logical place. * dev: Correct the order to load configuration files to support VS Code Ext * dev: Normalize globs passed in on the command line. - Added lots of test to ensure behavior. - Added support for `files` to be defined in the configuration. - Fixed some issues related to the root. * dev: build lists of include and exclude globs. * dev: File normalization is now done in cspell-glob. * dev: Use a generator to flatten the results and make them unique. * dev: Normalize relative paths * dev: Use a single glob. * dev: make single glob optional * Use 0.2 for the main cspell.json file * Update launch.json
With version 5.3.0 it is possible to add a
|
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. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Is your feature request related to a problem? Please describe.
It is now not possible to run cspell without specifying the patterns of files with the command. There is one workaround via
excludePaths
that has a large performance hit:And then excluding everything again, except the suspects:
This results in only the
README.md
being spell checked. Great. Not performant though.Describe the solution you'd like
add
includePaths
so that we don't have to specify any pattern and can just runcspell
, which will find all it needs in it's config to operate on.Additional context
When working with a lot of projects it becomes cumbersome to have to maintain configuration in multiple places. It is preferable to be able to just call a command without parameters, and copy over a file from another project and just edit that, instead of invocations.
The text was updated successfully, but these errors were encountered: