Add fuzzy/typo-tolerant matching for component name and I/O fields#2427
Open
Mbeaulne wants to merge 1 commit into
Conversation
🎩 PreviewA preview build has been created at: |
This was referenced Jun 18, 2026
Collaborator
Author
|
Warning This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
This stack of pull requests is managed by Graphite. Learn more about stacking. |
7 tasks
Mbeaulne
changed the title
8 tasks
This was referenced Jun 18, 2026
Mbeaulne
commented
Jun 18, 2026
Mbeaulne
commented
Jun 18, 2026
Mbeaulne
force-pushed
the
06-18-improve_component_search_scoring_relevance
branch
from
bbd53a7 to
36032c1
Compare
Mbeaulne
force-pushed
the
06-18-add_safe_typo_tolerance_for_names_and_io_fields
branch
2 times, most recently
from
0a7d588 to
e379e64
Compare
Mbeaulne
force-pushed
the
06-18-improve_component_search_scoring_relevance
branch
from
36032c1 to
d8e31f8
Compare
Mbeaulne
force-pushed
the
06-18-add_safe_typo_tolerance_for_names_and_io_fields
branch
from
e379e64 to
89029f0
Compare
Mbeaulne
force-pushed
the
06-18-improve_component_search_scoring_relevance
branch
from
d8e31f8 to
d4d0a60
Compare
Mbeaulne
force-pushed
the
06-18-add_safe_typo_tolerance_for_names_and_io_fields
branch
from
89029f0 to
fc80727
Compare
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
1 participant
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.
Description
Adds typo tolerance to the lexical search functionality for component names and input/output fields. When a query token is 4–6 characters, a single-character edit distance is allowed; for tokens 7+ characters, up to two edits are permitted. Fuzzy matches receive a slightly lower score than exact matches via a dedicated
FUZZY_MATCH_BONUS_MULTIPLIER. Typo tolerance is intentionally restricted tonameandiofields — descriptions and implementation text do not benefit from fuzzy matching to avoid noisy results.The implementation uses a standard dynamic programming Levenshtein distance algorithm with an early-exit optimisation that abandons the computation once the running row minimum exceeds the allowed distance.
Related Issue and Pull requests
Type of Change
Checklist
Screenshots (if applicable)
Test Instructions
filtr(forfilter_rows) anddatset(fordataset) return the correct component.xgbost) return no results.Additional Comments
Fuzzy matching is skipped entirely when the computed max edit distance is 0 (tokens shorter than 4 characters), keeping short-token searches fast and precise.