Replies: 0 comments 1 reply
-
one thing I'd like to change about state-results (in a major version or via a prop to enable it) is to actually do return (empty) items in init and rendering the children using it, to prevent issues like algolia/vue-instantsearch#935 see: |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Feature ⚡️
As a Vue InstantSearch user, I'd like to be able to access data of scopedResults from ais-state-results.
What is your use case for such a feature?
Say I have an InstantSearch instance with two indices side by side:
demo_ecommerce
anddemo_media
I'd like to be able to show the total number of hits for my query, for the two indices.
nbHits of demo_ecommerce + nbHits of demo_media
demo
Currently I can do this with ais-autocomplete because it's one of the few widgets that's able to access
scopedResults
and exposes it in a slot. But I think it's more natural to do withais-state-results
.What is your proposal
scopedResults
, maybe evenindices
similarly to connectAutocompleteBeta Was this translation helpful? Give feedback.
All reactions