Skip to content

Match release-profile exclusions on whole words - #58

Merged
JeremiahM37 merged 2 commits into
JeremiahM37:mainfrom
vedhavyas:fix/release-profile-word-bounds
Sep 29, 2026
Merged

JeremiahM37 merged 2 commits into
JeremiahM37:mainfrom
vedhavyas:fix/release-profile-word-bounds

Conversation

@vedhavyas

Copy link
Copy Markdown
Contributor

must_not_contain was matching as a case-insensitive substring, so a title was dropped whenever the entry's letters appeared inside a longer word - RAT removed ENTITY: THE BLACK DAY - v1.01 + Operative DLC v0.2 [FitGirl Repack] on the "Operative" in it, with nothing logged. I've made exclusion entries match a whole word, bounded on both sides.

vedhavyas and others added 2 commits September 28, 2026 14:05
A must_not_contain entry was matched as a substring, so a title carrying its
letters anywhere was dropped: RAT removed "ENTITY: THE BLACK DAY - v1.01 +
Operative DLC v0.2 [FitGirl Repack]" on the rat in "Operative", with nothing
logged and no way to tell the profile caused it. Exclusion entries now match a
whole word, bounded by a non-alphanumeric character or the string edge on both
sides.

must_contain and preferred keep the substring form deliberately - their entries
are fragments on purpose, so bounding MULTi would stop it scoring MULTi12 on the
seeded default profile. The tests pin both directions of the exclusion change,
and pin that asymmetry.
@JeremiahM37
JeremiahM37 merged commit 86b5d4c into JeremiahM37:main Sep 29, 2026
3 checks passed
@vedhavyas
vedhavyas deleted the fix/release-profile-word-bounds branch September 30, 2026 03:34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants