Add ignore_separators option to by_name() - #105
Merged
apdavison merged 3 commits intoSep 12, 2026
Merged
Conversation
apdavison
approved these changes
Sep 11, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds a new
ignore_separatorsoption toby_name(), plus a small efficiency fix in the same code path.ignore_separatorsoption: whenTrue, hyphens (-), underscores (_), slashes (/), and repeated whitespace are all treated as a single space before matching. For instance,"CLARITY-TDE"or"CLARITY TDE"now match the canonical"CLARITY/TDE"Technique.normalize(name)was being recomputed on every iteration of the lookup loop even though the query never changes within a call; it's now computed once per call instead.ignore_separators.