You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This would check to see if there are 3 or fewer changes to "fix" the string. We can adjust this limit as needed, but not too much as a large limit will start matching other unrelated items
This will be a bit more complicated than the snippet above. While that works for https://old.reddit.com/r/climbing/comments/uq7ej2/sent_my_first_v8_thin_lizzy_in_joshua_tree it doesn't work for the "Yak Crack" example. If we're using a levenshtein distance of <= 3, then that means "Yak Crack" can match just about any "___ Crack" route (which means that in our cutoff of !searchResult.IsEmpty() && searchResult.AllResults.Count < 75, 75 is too low)
For instance, in https://www.reddit.com/r/climbing/comments/715awf/red_rock_season_is_back_cruisin_up_yak_crack_511c/ the user mentioned that they are climbing "Yak Crack". While there are some results with that name, the real result is actually "Yaak Crack". We should implement fuzzy query matching so that "Yaak Crack" would also come up in the results list.
The text was updated successfully, but these errors were encountered: