Skip to content
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

[Feature Request]: Somehow weaken typo matches (not exact, but caught in Levenshtein distance) #156

Open
dpasque opened this issue Jul 25, 2023 · 0 comments
Labels
[Type] Feature Request Enhancement ideas

Comments

@dpasque
Copy link
Contributor

dpasque commented Jul 25, 2023

"What": What is your idea?

Right now, we allow a little bit of search fuzziness in our searches -- essentially allowing for typos. We scale based on length, but for most words, you can have 1 character wrong. This makes the search more forgiving, allowing for common typos both for searchers and issue reporters.

But, this can also be a nuisance on occasion! See issue #150 -- photon is one edit away from photos -- which is unfortunately a pretty common word.

We should find a way to soften those cases.

"Why?": Why would this be impactful?

In certain cases, helps you more accurately find the issue you're looking for.

"How?" How should this feature work?

Couple of ideas:

  • See if ElasticSearch has the ability to score issues that typo match lower than ones that don't.
  • See if there's a way to turn off typo matching if the term is put in quotes.
@dpasque dpasque added the [Type] Feature Request Enhancement ideas label Jul 25, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
[Type] Feature Request Enhancement ideas
Projects
None yet
Development

No branches or pull requests

1 participant