Override glob recursive does not work as expected.

[infacto]

Hi, maybe my fault but the following doesn't work:

.vscode/settings.json

{
  "cSpell.overrides": [
    {
      "filename": "assets/i18n/**/xx.json",
      "language": "en,xx"
    }
  ]
}

Result:

• assets/i18n/xx.json (works)
• assets/i18n/sub/xx.json (doesn't work)

^{(xx is just a placeholder for this example here)}

I have to change filename to assets/**/xx.json to work for both. But I wonder how to specify the i18n folder as itself and recursive?

https://github.com/streetsidesoftware/cspell/blob/main/docs/configuration/overrides.md

Updated: Changed override to overrides in this example. Just a typo.

[Jason3S]

@infacto,

This seem more like an issue than a discussion.

It should work like you expect.

[Jason3S]

@infacto,

Some things to try:

1. In the example given, "cSpell.override": should be "cSpell.overrides".
   Note: Due to the way VS Code settings are assembled, it is difficult for an extension to know where a setting came from. Because of that, relative paths are problematic. See if "filename": "**/assets/i18n/**/xx.json", works for you. Adding the ** to the beginning of the blob allows it to match any prefix.

2. Use a cspell config file.
   Please try adding a cspell.json or cspell.config.yaml file to the root of your repository:

   cspell.json

   {
     "overrides": [
       "filename": "assets/i18n/**/xx.json",
       "language": "en,xx"
     ]
   }

3. A a cspell section to the package.json file.

   package.json

   "cspell": {
     "overrides": [
       "filename": "assets/i18n/**/xx.json",
       "language": "en,xx"
     ]
   }

[infacto]

Thanks, it's "overrides" in my settings. Just a typo in this example here. Sorry. But I found a bug in my brain. Too embarrassing to tell here. It was a sibling dir (glob: assets/(one|two)/xx.json or just assets/**/xx.json), not a sub dir. 🤦‍♂️ It just looked like a sub dir in my overview because same prefix (different from this example). I'm a confused old man. ^^ Uh, could we just delete this? 👀 And never talk about it again? Sorry and thanks anyway.

[Jason3S]

@infacto,

Thank you for letting me know. I think it might be useful for other people that run into similar issues. I'm sure you are not the only one.

But, if you like, I can remove it.