How to disable all rules for one sub-directory?

[marians]

We are about to get started using Vale on our documentation repository. There is one sub folder in that repo which we'd like to exclude from linting, but I can't figure out how that's done.

I see no way to just exclude a single path in any way. So now I'm trying to create a .vale.ini in the subfolder that should be excluded, with all rules set to NO. This isn't working, all rules are applied to the subfolder's content, too.

What am I missing? This must be a common use case. Thanks for your help.

[marians]

For more details, I'm taking this approach from this docs paragraph

Vale expects its configuration to be in a file named .vale.ini or _vale.ini. It’ll start looking for this file in the same folder as the file that’s being linted. If it can’t find one, it’ll search up the file tree.

Here is the layout of my test setup:

├── .vale.ini
├── content
│   ├── bad
│   │   ├── .vale.ini
│   │   └── content.md
│   └── content.md
└── vale-styles
    ├── .vale-config
    │   └── 0-Hugo.ini
    └── Microsoft
        ├── AMPM.yml
        ├── ...

Content of .vale.ini:

StylesPath = vale-styles

Packages = Hugo, Microsoft

[*.md]
MinAlertLevel = suggestion
BasedOnStyles = Vale, Microsoft

Content of content/bad/.vale.ini:

StylesPath = ../../vale-styles

Packages = Hugo, Microsoft

[*.md]
MinAlertLevel = suggestion
BasedOnStyles = Vale, Microsoft

Microsoft.Contractions = NO
Microsoft.We = NO
Vale.Spelling = NO

Content of content.md:

# Headline

We are a company using lots of TLAs.

Result of executing vale content/bad/content.md:

 content/bad/content.md
 3:1   warning  Try to avoid using              Microsoft.We
                first-person plural like 'We'.
 3:1   error    Use 'we're' instead of 'We      Microsoft.Contractions
                are'.
 3:32  error    Did you really mean 'TLAs'?     Vale.Spelling

✖ 2 errors, 1 warning and 0 suggestions in 1 file.

[marians]

I looked into the --glob option more and with the help of some googling found this solution:

vale --glob='!content/bad/**' .

While this works, I would still like to understand why the approach I tried did not work. I expected the .vale.ini closest to the linted file to become effective.

[jdkato]

If you want to ignore a sub-directory entirely, then --glob is the way to do.

If you want to change or override config values for a certain sub-directory, you can do so with just the root .vale.ini file:

StylesPath = vale-styles

Packages = Hugo, Microsoft

[*.md]
MinAlertLevel = suggestion
BasedOnStyles = Vale, Microsoft

[content/bad/*.md]
Microsoft.Contractions = NO
Microsoft.We = NO
Vale.Spelling = NO

[marians]

Thanks, that helped! It didn't occur to me that it's possible to use path patterns in the square brackets.