Add an option to expose the allowMidWordMatch as a setting#152292
Add an option to expose the allowMidWordMatch as a setting#152292jrieken merged 24 commits intomicrosoft:mainfrom etriebe:etriebe/add_firstmatchcanbeweak_option
Conversation
jrieken
left a comment
There was a problem hiding this comment.
Thanks so far. This is already looking quite good. I left a few nit comments for seemingly un-needed changes (please PR minimally). We also need to come up with a good name, IMO firstMatchCanBeWeak is too technical to expose it as user-facing setting
@jrieken what about allowMidWordMatch? Because I think this is what this current change will do. Or we change logic to have the inverse, which is something like, forceFirstTypedCharacterToBeStartOfWord or forceMatchOnStartOfWord. I might prefer the second. |
|
@jrieken all issues should be resolved besides the name choice which I'd love your feedback on before making a choice. Also, as an aside, what formatter do you use for format document to work to avoid hygiene issues? I used prettier and then the whole doc changed significantly. |
|
Any chance you can take a look? @jrieken |
|
Sorry - I have been swapped recently and I am now heading out to a longer vacation. My plan is to finally pick this up in August. Thanks for being patient. |
All good! Thanks for the heads up! We're going to work on a fix internally for now and will revert that once this lands here. 😀 |
|
Any chance you'll be able to take a look for August? @jrieken |
jrieken
left a comment
There was a problem hiding this comment.
Thanks. I have pushed a change with the new name for this (matchOnWordStartOnly) and this is now ready to be merged
This PR fixes #53715
This won't change the default experience but will give people an option to change the fuzzy search algorithm that is used.
How to test: