Documentation Index
Fetch the complete documentation index at: https://algolia.com/llms.txt
Use this file to discover all available pages before exploring further.
By default, InstantSearch sends an initial to Algolia’s servers with an empty .
This connection helps speed up later requests.
However, sometimes you don’t want to perform more network calls than are necessary.
For example, you may want to limit the number of search requests and reduce your overall Algolia usage.
This guide helps you build a UI that prevents this initial request.
How a search client works
InstantSearch is the UI layer that sits on top of Algolia’s search client layer,
with a state managed by the Algolia search helper layer.
These three layers are interchangeable so that you can use the InstantSearch widgets with a different search client.
The search client queries Algolia’s servers whenever users refines a search.
You can build a custom search client to add custom behavior.
For example,
to perform backend searches with InstantSearch.
Implementing a proxy
To prevent the initial empty query, you must wrap a custom search client around Algolia’s,
and pass it to ais-instant-search.
The custom search client acts as a proxy for search requests:
<template>
<ais-instant-search
:search-client="searchClient"
index-name="instant_search"
>
<ais-search-box />
<ais-hits />
</ais-instant-search>
</template>
<script>
import { liteClient as algoliasearch } from 'algoliasearch/lite';
const algoliaClient = algoliasearch(
'ALGOLIA_APPLICATION_ID',
'ALGOLIA_SEARCH_API_KEY'
);
const searchClient = {
...algoliaClient,
search(requests) {
return algoliaClient.search(requests);
},
};
export default {
data() {
return {
searchClient,
};
},
};
</script>
search method.
In this case, you only call it when performing a query.
You can also use a proxy to only begin searching after a certain number of characters have been typed by adding a condition, for example, query.length > 3.
Detecting empty search requests
If you don’t want to perform a search request when the query is empty (""),
you need to detect it:
const searchClient = {
...algoliaClient,
search(requests) {
if (requests.every(({ params }) => !params.query)) {
// Here we have to do something else
}
return algoliaClient.search(requests);
},
};
Sometimes, one user action results in multiple queries, for example, clicking on an ais-refinement-list or using multiple ais-index widgets. Make sure that every query is empty before intercepting the function call. requests array. Each object requires at least these properties: hits, nbHits, and processingTimeMS.
const searchClient = {
...algoliaClient,
search(requests) {
if (requests.every(({ params }) => !params.query)) {
return Promise.resolve({
results: requests.map(() => ({
hits: [],
nbHits: 0,
nbPages: 0,
page: 0,
processingTimeMS: 0,
hitsPerPage: 0,
exhaustiveNbHits: false,
query: "",
params: "",
})),
});
}
return algoliaClient.search(requests);
},
};
ais-instant-search widget, like this:
<template>
<ais-instant-search
:search-client="searchClient"
index-name="instant_search"
>
<p>The request is only triggered once the query is not empty.</p>
<ais-search-box />
<ais-hits />
</ais-instant-search>
</template>
<script>
import { liteClient as algoliasearch } from 'algoliasearch/lite';
const algoliaClient = algoliasearch(
'ALGOLIA_APPLICATION_ID',
'ALGOLIA_SEARCH_API_KEY'
);
const searchClient = {
...algoliaClient,
search(requests) {
if (requests.every(({ params }) => !params.query)) {
return Promise.resolve({
results: requests.map(() => ({
hits: [],
nbHits: 0,
nbPages: 0,
page: 0,
processingTimeMS: 0,
hitsPerPage: 0,
exhaustiveNbHits: false,
query: '',
params: '',
})),
});
}
return algoliaClient.search(requests);
},
};
export default {
data() {
return {
searchClient,
};
},
};
</script>
