Set one vocabulary as error, another as warning?

[amyq]

Check for existing issues

• Completed

Describe the feature

Is it possible to declare one vocabulary's findings as error and another as warning? We haven't converted from our in-house spelling rule to a vocabulary for … $reasons. I expect to be asked if we could implement something like:

• vocab 1, internal: incorrect capitalization of our company's products should be error because we REALLY care about these, they're our legal wordmarks and we DO want to break a pipeline if these are used incorrectly.
• vocab 2, other: while we want to fix all spelling issues, we have a LOT of exceptions in our huge docset, and we don't want to break a pipeline for these. Set these to warning?

For now, we have a REALLY dodgy workaround 🙈 but maaaaaaan, do I ever want to get those case-specific terms pried out of our .markdownlint-cli2.yaml file and reunited with the rest of our spelling work.

[jdkato]

I'm not totally sure I understand the request, but to be clear: in Vale, spelling and capitalization treated as distinct topics.

spelling-based rules and vocabularies are complementary features -- not something that you'd convert to (or from):

• Spell check is case-insensitive and operates on single words.
• Vocabularies are case-sensitive and operate on arbitrary regex.

So, for example, I'd add something like "autocomplete" to a dictionary (or an ignore file) and something like "GitLab Pages" to a vocabulary.

If I'm understanding correctly, you're asking for the ability to add a word like "JavaScript" to a vocabulary and raise a warning (instead of an error) for occurrences like "Javascript"?