Hey Waqar, and thanks.
Unfortunately, both options are necessary in certain views.
As a workaround, I had to build the filter in jQuery for this view, and in another view (the one we chatted about, which showed me items with 0 relevance) I also had to use jQuery to hide these.
So what you're saying is toolset is problematic for large sites? Isn't there a way to make things work as they should?
1. For an issue to qualify as a bug, it needs to be reproducible on a clean install, without any extra plugins or themes.
( in our extensive tests this case failed )
2. For an issue to qualify as a compatibility issue with a particular third-party theme or a plugin, it needs to be reproducible on a clean install, with only Toolset plugins and that theme or plugin.
( in our extensive tests this case failed too with Toolset + WooCommerce + Elementor Pro )
3. When an issue is specific to a particular install, it is considered an exception, and further dubbing into this exception is not possible as we already know that an expensive operation is being attempted on a website with a large amount of data and in the presence of a number of third-party plugins and custom code, which would eventually result in unexcepted results/behavior. This is the reason, why I recommended staying with the jQuery workaround that you've already implemented.