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
{{ message }}
This repository has been archived by the owner on May 10, 2022. It is now read-only.
cancelRequests is a very useful feature setting and should be enabled by default.
We had not noticed autoComplete does not automatically cancel requests (or discard them for other reasons, e.g. since it realized better results were already received) because we are developing on a single-threaded server. Only when we deployed in a multi-threaded environment with real data (where queries for shorter terms return more results, thus take longer to transfer!), we realized this feature was actually off. It is not even documented in the README.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
cancelRequests is a very useful feature setting and should be enabled by default.
We had not noticed autoComplete does not automatically cancel requests (or discard them for other reasons, e.g. since it realized better results were already received) because we are developing on a single-threaded server. Only when we deployed in a multi-threaded environment with real data (where queries for shorter terms return more results, thus take longer to transfer!), we realized this feature was actually off. It is not even documented in the README.
The text was updated successfully, but these errors were encountered: