docs: document aggregateContent, make API ref clearer#1328
Conversation
|
✔️ Deploy Preview for docsearch ready! 🔨 Explore the source changes: 559baa8 🔍 Inspect the deploy log: https://app.netlify.com/sites/docsearch/deploys/62331aa48e9077000851648a 😎 Browse the preview: https://deploy-preview-1328--docsearch.netlify.app |
|
This pull request is automatically built and testable in CodeSandbox. To see build info of the built libraries, click here or the icon next to each commit SHA. Latest deployment of this branch, based on commit 559baa8:
|
| Contains values that can be used as [`facetFilters`][15] | ||
| Custom variables are used to [`filter your search`](/docs/DocSearch-v3#filtering-your-search), you can define them in the [`recordProps`](#indexing-content-for-faceting) | ||
|
|
||
| ## `helpers.docsearch` API Reference |
There was a problem hiding this comment.
Can be merged as-is but belongs into official documentation not here
https://www.algolia.com/doc/tools/crawler/apis/configuration/actions/#parameter-param-recordextractor
There was a problem hiding this comment.
I did not found any mention of it on the Algolia doc so I've only added here for now. To avoid duplicate, a doc should point to the other, feel free to decide!
There was a problem hiding this comment.
well it's already decided, official doc first :D
but can be done later don't worry
2 participants
Summary
This PR documents the new
aggregateContentoption available on the crawler.This option allows users to reduce the number of records outputted by the crawler by aggregating all the records of type
contentin a single record.