-
-
Notifications
You must be signed in to change notification settings - Fork 65
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Reasons for not working queryRule #151
Comments
While Typesense server supports query rules (called overrides / curation in Typesense), we don't support returning custom data or context in overrides yet. So we would need to first add these features to Typesense server, before we can add support in the adapter. Could you open separate issues for each in Typesense repo, along with your use-case for each of these? We can then prioritize based on demand. |
I believe that if we do at least part of this element - and suggestions (out of the box), we can chase even algolia very quickly. I think that dynamic widgets were already a milestone. Because it's such a hot feature. |
Hello @jasonbosco. |
From what I can see there is no problem to implement this. Even if we download e.g. "banners" from an external collection - we use multisearch after all. Let's do that and typesense will be fully ready replacement instead of algolia. |
In the case of dynamicWidgets, it requires facet data and this information is already returned by the Typesense Server API response and this adapter just transforms those facet counts to a format that dynamicWidgets understands. But in the case of the query rules related widgets, the Typesense Server API does not return the data required to transform it to the instantsearch format, since Typesense Server API does not support these particular features (query rule context and query rule user data)... If you're anyway using multi-search to download banners, one thing you could do is, use |
For what technical reasons are these features not working with the latest typesense?
queryRuleCustomData
queryRuleContext
The text was updated successfully, but these errors were encountered: