You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Spelling.yml has filter regex terms that filter more words than should be. This leads to words that begin with these regex filter terms to be ignored from the spell check.
Examples:
These words should trigger a Vale RedHat.Spelling alert but do not: subcomamnd, Developper, cherrry, et. al.
Here are the filter terms from Spelling.yml relevant to these words:
- "[cC]he"
- "[Ss]u"
- Dev
These are just a few examples. There are likely more filter terms that could prefix other words.
To fix, add a regex word boundary \b after these terms. For example:
- "[cC]he\b"
- "[Ss]u\b"
- Dev\b
Add a regex word boundary after other filter terms that might preface longer words. Possibly consider adding a regex word boundary after every filter term in Spelling.yml, just in case?
I would be happy to submit a pull request for the latter solution.
The text was updated successfully, but these errors were encountered:
emteelb
changed the title
Spelling.yml filtering words partials leading to misspellings not being flagged
Spelling.yml filters word partials leading to misspellings not being flagged
Oct 16, 2024
Spelling.yml
has filter regex terms that filter more words than should be. This leads to words that begin with these regex filter terms to be ignored from the spell check.Examples:
RedHat.Spelling
alert but do not: subcomamnd, Developper, cherrry, et. al.Here are the filter terms from
Spelling.yml
relevant to these words:These are just a few examples. There are likely more filter terms that could prefix other words.
To fix, add a regex word boundary
\b
after these terms. For example:Add a regex word boundary after other filter terms that might preface longer words. Possibly consider adding a regex word boundary after every filter term in
Spelling.yml
, just in case?I would be happy to submit a pull request for the latter solution.
The text was updated successfully, but these errors were encountered: