Adjusting Result Item Numbering Across Pagination
TLDR A asked how to adjust numbering across pages of search results. Kishore Nallan suggested a CSS rule, while Greg advised using array indices or the
start attribute. Jason referred to using __hitIndex in instantsearch.
Feb 05, 2022 (21 months ago)
Kishore Nallan11:50 AM
Kishore Nallan01:30 PM
Kishore Nallan01:32 PM
<li>-- that explains those 1 to 10 numbering.
Kishore Nallan01:34 PM
list-style: nonerule to remove that numbering, but Jason might have an alternative approach here.
ul(unordered list) instead of
index + 1if you don't)
<ol>element there is a
startattribute that lets you set the number sequence starting point
Indexed 2779 threads (79% resolved)
Resolve Facets and Sorting Issues with Typesense
Ethan needed assistance with getting all facet values and sorting results by date using Typesense. Jason provided guidance on how to use Typesense properties to accomplish these tasks, and resolved issues related to specific use-cases provided by Ethan and Rushil.
Troubleshooting Typesense Setup and Understanding Facets and Keywords
Demitri encountered errors when exploring Typesense for the first time. Jason guided them through troubleshooting and discussed facets, keyword settings, and widget configurations. Helin shared a Python demo app and its source code to help Demitri with their project.
Hiding Exact Hits Number in Typesense and Utilizing `out_of` Field
A sought a way to hide exact hits count in Typesense. Kishore Nallan clarified about the `out_of` field, its future use, and suggested using `found` for scrolling. Jason offered a solution to hide the count by modifying the item template.
Range Filtering and Faceting Discussion
Phil asked about the requirements for range filtering, which Jason explained does not always require faceting. Discussion about different possibilities with Algolia and Typesense ensued, resulting in Phil successfully utilizing the 'Configure' widget.
Querying with Typesense-Js and Handling Null Values
michtio was querying using typesense-js and receiving fewer results than expected. Kishore Nallan suggested using different query parameters. Further discussion led to the handling of 'null' values and filtering syntax in the search queries. The thread ended with Jason offering migration support from Algolia to Typesense.