-
## Description
I am using TS example of `next` implementation https://github.com/typesense/showcase-nextjs-typesense-ecommerce-store. It still uses the old way of `react-instantsearch-dom/server` i…
-
## Issue
Facets do not update the hit results when placed in a separate Index component, even with the same indexId.
## Description
We currently have the search working without federated, using…
-
### 🐛 Current behavior
Inside `.queries[0]`: Attribute `shift_schedule:01:00 PM - 01` is not filterable.
I am passing value `01:00 PM - 01:30 AM`
Which is read as `"shift_schedule:01:00 PM - 01"=…
-
This is more of a question than an issue.
I see the problem on line 548 of formatted minified file. I do not have react in my project, do we need react for this widget to work? I also use the preact…
-
**Description**
Hello!
I have a simple search app using Gatsby, Meilisearch, and Instantsearch. I'm using Meilisearch Cloud as well.
Search and all that works great. I wanted to fine tune t…
-
This issue lists Renovate updates and detected dependencies. Read the [Dependency Dashboard](https://docs.renovatebot.com/key-concepts/dashboard/) docs to learn more.
> [!WARNING]
These dependencies …
-
### 🐛 Current behavior
### Insights track called multiple times
Insights track function is called as many times as the useHits hook or Hit component are used in the InstantSearch component.
…
-
**Description**
I have an index I am using geosearch on, using `instant-meilisearch` + `react-instantsearch`. Something I noticed is that when I try to use `hit.objectID` for anything, it's never the…
queer updated
1 month ago
-
## Description
Hi, we were wondering how do we have multiple instant search clients (Typesense Wrapper int he screenshots) co-existing and working in the same form.
One instant search client poin…
-
### Info
Looks like algolia needs to be setup first, possibly something to do with `react-instantsearch` and `react-instantsearch-dom`
```
TypeError: Cannot read property 'store' of undefined
…