infiniteHits
infiniteHits({ container: string|HTMLElement, // Optional parameters escapeHTML: boolean, showPrevious: boolean, templates: object, cssClasses: object, transformItems: function, cache: object, });
1
import { infiniteHits } from 'instantsearch.js/es/widgets';
About this widget
The infiniteHits
widget displays a list of results with a “Show more” button at the bottom of the list. As an alternative to this approach, the infinite scroll guide describes how to create an automatically-scrolling infinite hits experience.
To configure the number of hits to show, use the hitsPerPage
widget or the configure
widget.
If there are no hits, you should display a message to users and clear filters so they can start over.
Examples
1
2
3
4
5
6
7
8
9
10
11
12
13
infiniteHits({
container: '#infinite-hits',
templates: {
item(hit, { html, components }) {
return html`
<h2>
${components.Highlight({ attribute: 'name', hit })}
</h2>
<p>${hit.description}</p>
`;
},
},
});
Options
Parameter | Description | ||
---|---|---|---|
container
|
type: string|HTMLElement
Required
The CSS Selector or |
||
Copy
|
|||
escapeHTML
|
type: boolean
default: true
Optional
Escapes HTML entities from hits string values. |
||
Copy
|
|||
showPrevious
|
type: boolean
default: false
Optional
Enable the button to load previous results. The button is only displayed if the routing option is enabled in |
||
Copy
|
|||
templates
|
type: object
Optional
The templates to use for the widget. |
||
Copy
|
|||
cssClasses
|
type: object
default: {}
Optional
The CSS classes you can override:
|
||
Copy
|
|||
transformItems
|
type: function
default: items => items
Optional
Receives the items and is called before displaying them. It returns a new array with the same “shape” as the original. This is helpful when transforming, removing, or reordering items. The complete If you’re transforming an attribute with the |
||
Copy
|
|||
cache
|
type: object
default: in-memory cache object
Optional
The widget caches all loaded hits. By default, it uses its own internal in-memory cache implementation. Alternatively, use You can also implement your own cache object with |
||
Copy
|
Templates
You can customize parts of the widget’s UI using the Templates API.
Every template provides an html
function you can use as a tagged template. Using html
lets you safely provide templates as an HTML string. It works directly in the browser without a build step. See Templating your UI for more information.
The html
function is available starting from v4.46.0.
Parameter | Description | ||
---|---|---|---|
empty
|
type: string|function
Optional
The template to use when there are no results. It exposes the |
||
Copy
|
|||
item
|
type: string|function
Optional
The template to use for each result. This template receives an object containing a single record. The record has a new property |
||
Copy
|
|||
showPreviousText
|
type: string|function
default: Show previous results
Optional
The template to use for the “Show previous” label. |
||
Copy
|
|||
showMoreText
|
type: string|function
default: Show more results
Optional
The template to use for the “Show more” label. |
||
Copy
|
HTML output
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
<div class="ais-InfiniteHits">
<button class="ais-InfiniteHits-loadPrevious">
Show previous
</button>
<ol class="ais-InfiniteHits-list">
<li class="ais-InfiniteHits-item">
...
</li>
<li class="ais-InfiniteHits-item">
...
</li>
<li class="ais-InfiniteHits-item">
...
</li>
</ol>
<button class="ais-InfiniteHits-loadMore">
Show more
</button>
</div>
Customize the UI with connectInfiniteHits
If you want to create your own UI of the infiniteHits
widget, you can use connectors.
To use connectInfiniteHits
, you can import it with the declaration relevant to how you installed InstantSearch.js.
1
import { connectInfiniteHits } from 'instantsearch.js/es/connectors';
Then it’s a 3-step process:
// 1. Create a render function
const renderInfiniteHits = (renderOptions, isFirstRender) => {
// Rendering logic
};
// 2. Create the custom widget
const customInfiniteHits = connectInfiniteHits(
renderInfiniteHits
);
// 3. Instantiate
search.addWidgets([
customInfiniteHits({
// instance params
})
]);
Create a render function
This rendering function is called before the first search (init
lifecycle step)
and each time results come back from Algolia (render
lifecycle step).
const renderInfiniteHits = (renderOptions, isFirstRender) => {
const {
object[] hits,
object[] currentPageHits,
object results,
function sendEvent,
boolean isFirstPage,
boolean isLastPage,
function showPrevious,
function showMore,
object widgetParams,
} = renderOptions;
if (isFirstRender) {
// Do some initial rendering and bind events
}
// Render the widget
}
Rendering options
Parameter | Description | ||
---|---|---|---|
hits
|
type: object[]
The matched hits from the Algolia API. This returns the combined hits for all the pages that have been requested so far. You can use Algolia’s highlighting feature with the |
||
Copy
|
|||
currentPageHits
|
type: object[]
The matched hits from the Algolia API for the current page. Unlike the |
||
Copy
|
|||
results
|
type: object
The complete response from the Algolia API. It contains the |
||
Copy
|
|||
sendEvent
|
type: (eventType, hit, eventName) => void
The function to send
Learn more about these events in the |
||
Copy
|
|||
isFirstPage
|
type: boolean
Indicates whether the first page of hits has been reached. |
||
Copy
|
|||
isLastPage
|
type: boolean
Indicates whether the last page of hits has been reached. |
||
Copy
|
|||
showPrevious
|
type: function
Loads the previous page of hits. |
||
Copy
|
|||
showMore
|
type: function
Loads the next page of hits. |
||
Copy
|
|||
widgetParams
|
type: object
All original widget options forwarded to the render function. |
||
Copy
|
Create and instantiate the custom widget
We first create custom widgets from our rendering function, then we instantiate them. When doing that, there are two types of parameters you can give:
- Instance parameters: they are predefined parameters that you can use to configure the behavior of Algolia.
- Your own parameters: to make the custom widget generic.
Both instance and custom parameters are available in connector.widgetParams
, inside the renderFunction
.
const customInfiniteHits = connectInfiniteHits(
renderInfiniteHits
);
search.addWidgets([
customInfiniteHits({
// Optional parameters
escapeHTML: boolean,
showPrevious: boolean,
transformItems: function,
})
]);
Instance options
Parameter | Description | ||
---|---|---|---|
escapeHTML
|
type: boolean
default: true
Optional
Escapes HTML entities from hits string values. |
||
Copy
|
|||
showPrevious
|
type: boolean
default: false
Optional
Enable the button to load previous results. |
||
Copy
|
|||
transformItems
|
type: function
default: items => items
Optional
Receives the items and is called before displaying them. It returns a new array with the same “shape” as the original. Helpful when transforming, removing, or reordering items. The entire If you’re transforming an attribute with the |
||
Copy
|
Full example
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
// Create the render function
const renderInfiniteHits = (renderOptions, isFirstRender) => {
const {
hits,
widgetParams,
showPrevious,
isFirstPage,
showMore,
isLastPage,
} = renderOptions;
if (isFirstRender) {
const ul = document.createElement('ul');
const previousButton = document.createElement('button');
previousButton.className = 'previous-button';
previousButton.textContent = 'Show previous';
previousButton.addEventListener('click', () => {
showPrevious();
});
const nextButton = document.createElement('button');
nextButton.className = 'next-button';
nextButton.textContent = 'Show more';
nextButton.addEventListener('click', () => {
showMore();
});
widgetParams.container.appendChild(previousButton);
widgetParams.container.appendChild(ul);
widgetParams.container.appendChild(nextButton);
return;
}
widgetParams.container.querySelector('.previous-button').disabled = isFirstPage;
widgetParams.container.querySelector('.next-button').disabled = isLastPage;
widgetParams.container.querySelector('ul').innerHTML = `
${hits
.map(
item =>
`<li>
${instantsearch.highlight({ attribute: 'name', hit: item })}
</li>`
)
.join('')}
`;
};
// Create the custom widget
const customInfiniteHits = connectInfiniteHits(
renderInfiniteHits
);
// Instantiate the custom widget
search.addWidgets([
customInfiniteHits({
container: document.querySelector('#infinite-hits'),
showPrevious: true,
})
]);
Click and conversion events
If the insights
option is true
, the infiniteHits
widget automatically sends a click
event with the following shape to the Insights API when a user clicks on a hit.
1
2
3
4
5
6
7
8
9
{
eventType: 'click',
insightsMethod: 'clickedObjectIDsAfterSearch',
payload: {
eventName: 'Hit Clicked',
// …
},
widgetType: 'ais.infiniteHits',
}
To customize this event, use the sendEvent
function in your item
template and send a custom click
event.
1
2
3
4
5
6
7
8
9
10
11
12
13
14
infiniteHits({
templates: {
item(hit, { html, components, sendEvent }) {
return html`
<div onClick="${() => sendEvent('click', hit, 'Product Clicked')}">
<h2>
${components.Highlight({ attribute: 'name', hit })}
</h2>
<p>${hit.description}</p>
</div>
`;
},
},
});
The sendEvent
function also accepts an object as a fourth argument to send directly to the Insights API. You can use it, for example, to send special conversion
events with a subtype.
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
infiniteHits({
templates: {
item(hit, { html, components, sendEvent }) {
return html`
<div>
<h2>${components.Highlight({ attribute: 'name', hit })}</h2>
<p>${hit.description}</p>
<button
onClick=${() =>
sendEvent('conversion', hit, 'Added To Cart', {
// Special subtype
eventSubtype: 'addToCart',
// An array of objects representing each item added to the cart
objectData: [
{
// The discount value for this item, if applicable
discount: hit.discount || 0,
// The price value for this item (minus the discount)
price: hit.price,
// How many of this item were added
quantity: 2,
},
],
// The total value of all items
value: hit.price * 2,
// The currency code
currency: 'USD',
})}
>
Add to cart
</button>
</div>
`;
},
},
});
Fields representing monetary values accept both numbers and strings, in major currency units (for example, 5.45
or '5.45'
). To prevent floating-point math issues, use strings, especially if you’re performing calculations.