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
Even if I set cache limit to 0, the search result always return cached result.
What happened is if I search "A", it shows result "AX", "AY","AZ" which is fine, but if I now search "B", it still show "AX", "AY", "AZ".
I have to manually clear cache to see new result.
The text was updated successfully, but these errors were encountered:
Thanks for creating an issue for this. I've run into that same annoyance myself but hadn't gotten around to fixing it. It's not that the search always shows the cached result, it's just that search results are persisted for 45 seconds – which can be annoying if you want to perform another search before 45 second has expired.
Anyway, I think I've come up with a working solution that isn't dependent on a timeout but still caches the results for filtering. You can checkout the feature/81-search-cache-improvements branch if you'd like to give it a shot.
Even if I set cache limit to 0, the search result always return cached result.
What happened is if I search "A", it shows result "AX", "AY","AZ" which is fine, but if I now search "B", it still show "AX", "AY", "AZ".
I have to manually clear cache to see new result.
The text was updated successfully, but these errors were encountered: