-
Notifications
You must be signed in to change notification settings - Fork 60
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
vue-instantsearch: Problems with search, letters disappear #644
Comments
I suffered from the same issue, managed to resolve it by using the debounced search box component provided in the Algolia documentation: |
Does the :stalled-search-delay has the same effect? https://www.algolia.com/doc/api-reference/widgets/instantsearch/vue/#widget-param-stalled-search-delay |
Hello @bmpf, sorry for this issue, the maintainer of this repo (@bidoubiwa) was not available the previous week, and is still not available this week. She will come back next Monday. Sorry for this bug, be sure she will take care of this bug as a priority when she'll come back :) |
Nope, I had tried it first, couldn't get the desired effect. Otherwise I wouldn't bother with creating a new component. |
Hello @curquiza , the solution given by @serdarcevher worked.
|
Weird, I didn't need to sync the URL params to make it work. Did you put it without the original ais-search-box component? This is the way I use it:
|
@serdarcevher Yes, It wouldn't sync with the url .
|
I mean, on refresh, the search keyword did not appear filled in the text box. |
Hello @bmpf and @serdarcevher what was the previous version of MeiliSearch you were using? |
Okey! After hours of trying things out, we think it is linked to the size of the components we ask vue-instantsearch to render. Because they do not have a debouncing system (while To solve the problem even faster you can reduce the paginationTotalHits which is set at 200 by default, for example by reducing it at Meanwhile, the debouncing solution suggested by Algolia for |
Hello, Current: Previous : |
I tried to reduce to 100 and the problem was still there.
That solution would be perfect. (Add option to re-fetch on every next-page and load more.)
Yes, its the solution for now. |
@bmpf if it's not to much to ask, i have a few more questions, if you are busy don't worry.
If you only have the answer to only a few questions, please feel free to ignore the others :) edit could you also add this widget?
It should show the processing time of each search |
I would suggest you to do 2 things that I have seen that the work amazingly!
and then use lodash debounce function
|
Closing this as it is not related to |
Description
When searching the first word, some letters disappear because of the high latency or big payload, is there a way of using a custom debouncer ? Or decrease the frequency of requests between typing letters.
Screenshots or Logs
Environment (please complete the following information):
EDIT:
This "problem" only happen after updating to the latest version, before that there was no "lagging". I've been using this for an year prior to this update.
The text was updated successfully, but these errors were encountered: