@blacs30 Got it. Man, appreciate your quick reply and help. Would be great if that action is configurable on the next release but it's not a high use case feature I guess. I'll keep an eye out in the next release and if it becomes urgent for me, I'll clone and compile locally.
Also, I just updated from v2.2.2 to v2.4.2 and while I'm using fuzzy filtering on both versions, after the update the fuzzy filtering seems to be drastically worse. i.e. prior to update, searching for Groupon would populate all the Groupon.com results at the top whereas post update maybe one would be at the top while another Groupon item would be like the 7th result.
I'm using fuzzy filtering bc I want to be able to populate results that contain rather than starts with my keyword.
I don't understand why fuzzy filtering results are worse now. Do you have any idea why and if it's fixable or possible to improve?
I set the env variable REORDERING_DISABLED to false to cache most used items (as a workaround) but I didn't have this set to false prior to updating.
Thanks!