-
Notifications
You must be signed in to change notification settings - Fork 0
fix: keep Russian root match from absorbing conjunctions #146
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
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -5,7 +5,7 @@ | |
| "id": "ru.obscene.huy.base", | ||
| "category": "OBSCENE_MAT", | ||
| "severity": "high", | ||
| "source": "ху[йяиёею]", | ||
| "source": "(?:хуй|хуя|хуи|хуё|хуе|хую)", | ||
|
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
Because each explicit alternative is still stretched, a following standalone word that starts with the same final letter is consumed as another repeat of that final atom. For example, Useful? React with 👍 / 👎. |
||
| "match": { | ||
| "strict": {}, | ||
| "loose": { | ||
|
|
||
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.
With this source split into fixed alternatives,
stretch: truecan only repeat the selected final letter, so inputs likeхуейorху-ейnow only produce aхуеprefix match; the loose boundary check then rejects it because the same token still has a trailingй. These are existing reviewed loose corpus cases intests/loose-corpus.spec.tsthat should be fully masked, so this change creates a bypass while fixing the following-conjunction case.Useful? React with 👍 / 👎.