Matched files change from 5.3.1 to 5.3.2

Info

Kind of Issue

• runtime - command-line tools
• building / compiling
• security
• change in behavior
• crash / error

Which Tool or library

• cspell – the command-line spelling tool
• cspell-tools – used for building dictionary files
• cspell-lib – library that does the actual spell checking.
• cspell-trie – tool for working with trie files.

Which Version

Version: 5.3.2 and up

Issue with supporting library?

• No
• Unsure
• cspell-glob – library for matching glob patterns
• cspell-io – thin file i/o library
• cspell-trie-lib - trie lib
• cspell-trie2-lib - trie lib alternate format

OS:

• Macos
• Linux
• Windows
• Other

version: 11.2.3

OS version if applicable.

Bug Description

Describe the bug

I have been using cspell as a linting script for nearly a year now, and have configured it to process “hidden files”. However, since 5.3.2 the glob pattern doesn’t seem to match the files in the same way. I can’t tell if issue comes from the matching glob or the configured ignorePaths being treated differently.

To Reproduce

I have set up a repo to reproduce the issue and see the clean run as before the issue presented.

Steps to reproduce the behavior:

1. Clone https://github.com/roydukkey/moist/tree/cspell/1114
2. Run yarn test:before, for the expected behaviour
   • Expects something similar to:

     moist % yarn test:before
     yarn run v1.22.10
     $ npx cspell@5.3.1 --config './.vscode/cSpell.json' '**/{.*/**/,.*/**/.,,.}*'
     1/5 ./.editorconfig 377.32ms
     2/5 ./.vscode -
     3/5 ./.vscode/cSpell.json 20.71ms
     4/5 ./package.json 6.11ms
     5/5 ./README.md 8.95ms
     CSpell: Files checked: 4, Issues found: 0 in 0 files
     ✨  Done in 1.39s.
     

3. Run yarn test:after, for the unexpected behaviour
   • Results like:

     moist % yarn test:after
     yarn run v1.22.10
     $ npx cspell@5.3.2 --config './.vscode/cSpell.json' '**/{.*/**/,.*/**/.,,.}*'
       1/128 ./.DS_Store 410.90ms
     /Users/roydukkey/Projects/moist/.DS_Store:2:20 - Unknown word (ebwspblob)
     /Users/roydukkey/Projects/moist/.DS_Store:2:33 - Unknown word (bplist)
     /Users/roydukkey/Projects/moist/.DS_Store:5:20 - Unknown word (Pathbar)
     /Users/roydukkey/Projects/moist/.DS_Store:6:22 - Unknown word (Srnlong)
     /Users/roydukkey/Projects/moist/.DS_Store:6:4372 - Unknown word (DSDB)
       2/128 ./.editorconfig 7.63ms
       3/128 ./.git -
       4/128 ./.git/COMMIT_EDITMSG 4.57ms
       5/128 ./.git/config 7.07ms
     /Users/roydukkey/Projects/moist/.git/config:2:2 - Unknown word (repositoryformatversion)
     /Users/roydukkey/Projects/moist/.git/config:3:2 - Unknown word (filemode)
     /Users/roydukkey/Projects/moist/.git/config:5:2 - Unknown word (logallrefupdates)
     /Users/roydukkey/Projects/moist/.git/config:6:2 - Unknown word (ignorecase)
     /Users/roydukkey/Projects/moist/.git/config:7:2 - Unknown word (precomposeunicode)
     /Users/roydukkey/Projects/moist/.git/config:8:2 - Unknown word (submodule)
     {...}
     /Users/roydukkey/Projects/moist/yarn.lock:92:1 - Unknown word (wrappy)
     CSpell: Files checked: 188, Issues found: 2424 in 51 files
     error Command failed with exit code 1.
     info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
     

Expected behavior

1. This **/{.*/**/,.*/**/.,,.}* pattern to match all files, including hidden files.
2. The ignorePaths configuration in ./.vscode/cSpell.json should properly exclude paths.

cspell.json

{
	"ignorePaths": [
		"node_modules",
		".git",
		"**/.DS_Store",
		"*.lock.json",
		"*-lock.json",
		"*.lock"
	],
	"dictionaries": [
	],
	// Before adding a word, see if there is already a dictionary in which it is contained.
	// http://github.com/streetsidesoftware/cspell-dicts
	"words": [
		"editorconfig",
		"roydukkey"
	]
}

Example Repository (Optional)

https://github.com/roydukkey/moist/tree/cspell/1114

[roydukkey]

@Jason3S Indeed. I have update the repo with test:workaround and test:fixed command to verify.

[github-actions[bot]]

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.