-
Notifications
You must be signed in to change notification settings - Fork 1.8k
QL: add "modelling/modeling" to ql/non-us-spelling
#7458
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
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
C# 👍
You could also add modelled/modeled. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Python looks good. One minor comment about the QL.
// analyses (as a noun) is fine | ||
s.regexpMatch(".*analyse[^s].*") and | ||
wrong = "analyse" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Perhaps it would make more sense to use an explicit word-boundary match, so something like s.regexpMatch(".*\\b" + wrong + "\\b.*")
.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good point.
But I think I'll wait with that until we encounter FPs.
With the current approach we also catch when the bad spelling is used as a prefix/suffix.
(But luckily English is not like Danish, so that will be rare).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
C++ 👍
/cc @intrigus-lgtm
I also made a patch thing that automatically fix the issues found by the new query.