Fixed when empty query added as bad query in case of no results#845
Fixed when empty query added as bad query in case of no results#845szabto wants to merge 1 commit intodevbridge:masterfrom
Conversation
There was an issue when empty query was ran but no result given, the code did not even try to query result when empty search did not give results.
|
Looks like that is by design, if there are no results, it would not try to query again. I don't see how it would not run a query. Did you set |
|
Sure I set it to My scenario is the following:
Everything is fine, when you have previously typed stuff, so if you have results for no typed characters. Currently I implemented this as a city lister and selector. |
|
What you are modifying is processResponse. That means there was a query and it is processing response. Maybe your problem is cache? Try disabling it and see how it works. |
|
The actual problem is here: If you write an empty search, and it gives no result, then it won't try to query anything else because of this But maybe this is working as designed, and needs to be workarounded with always non empty result for "" search. |
There was an issue when empty query was ran but no result given, the code did not even try to query result when empty search did not give results.