-
Notifications
You must be signed in to change notification settings - Fork 31
fix: scope of specific rules #138
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
I tested this in Ops docs and it checked the content that I was expecting, with no false positives. The error count was >4 times higher. But I'm not unhappy, as I have more confidence in the spellchecker! (And in the case of Ops, many of those errors are the same words over and over again - e.g., databag) |
@SecondSkoll I did a bit more testing in the Ops docs. There's a very small number of false positives from our .rst files that include the Ops package source.
|
Could you retest when you have a chance? I've added two tokenignores for RST directive options (though it will only work for one word passed to an option), and a filter for spelling which should eliminate |
The latest changes work, thanks!
I'm less sure about excluding |
Looks like the default Vale filters for spelling exclude hyphenated words. This might be down to the fact most dictionaries have little support for hyphenated words, but I'm unsure. I can update the filters, but it'll mean all hyphenated words need to be added to the ignore list. |
After trying the updated filters in 345c62b, I got approx 140 extra spelling errors, most of which I'd need to add to the exclude list. Michael and I just had a discussion and I feel that |
Summary scope seems to be bugged, using "sentence" scope seems to work a lot better.