feat(weir): add BoarderBorder rule to catch boarder/border word confusion#3481
feat(weir): add BoarderBorder rule to catch boarder/border word confusion#3481jlaportebot wants to merge 2 commits into
Conversation
hippietrail
left a comment
There was a problem hiding this comment.
Watch out with overusing "typo".
|
|
||
| let message "Did you mean `border`?" | ||
| let description "Flags likely typo cases where `boarder` (a lodger) appears where `border` (an edge/boundary) is expected." | ||
| let kind "Typo" |
There was a problem hiding this comment.
This is almost never a typo. I asked Google AI for the difference:
A typo happens when you know how to spell a word, but your fingers hit the wrong key, slip, or you type too fast. You meant to type "the", but accidentally hit "teh". It is a physical "slip of the hand".
The other kind is an actual spelling mistake. This occurs when you do not know the correct spelling of a word and mistakenly spell it the wrong way (e.g., spelling "definitely" as "definately").
|
Good point, @hippietrail! I've updated the rule:
This aligns with other similar Weir rules like |
|
Thanks for the feedback @hippietrail — I completely agree. This is a spelling confusion, not a typo. The current version of the rule already uses |
|
Good point about the distinction. The rule already uses |
37b6ebc to
bc98dbb
Compare
…sion Flags boarder when used in contexts where border (edge/boundary) is intended: - boarder of/between/around/with/on + cross the boarder - Does NOT flag legitimate lodger-sense boarder - Uses WordChoice kind (not Typo) — this is a word confusion, not a typo Closes Automattic#3471
bc98dbb to
e9aa462
Compare
@/tmp/pr3481_body.md