-
Notifications
You must be signed in to change notification settings - Fork 386
Ability to persist a widget #14
Comments
Another possibility here is to actually use another |
Yes this would be very helpful. |
I also see this as a problem as I have it set up in the header of my page, and every navigation between pages causes another POST In turn I have about 2200 requests while dev (out of 100k) which will quickly fill up when it goes live. I'm thinking about creating a component with it at the top-most parent and passing it down, perhaps it won't re-render when the component itself gets re-rendered, but we'll see how it goes |
@mclapa Thread hijacker, no thread hijacking! |
I'm closing this as for now I don't have a really good API proposal that would fix everything. Our getting started explains how to get along this, feel free to comment/open a new issue if necessary or if you have a proposal :) |
Use case
You have a mobile app using React Native and you want to use a modal to display some filters. When this modal is closed, the widgets that sets the refinements are unmounted, therefore, they're not in the state anymore. see: algolia/instantsearch#2069
Need
Being able to say that a widget is persistent. That way its state will remain and can still be applied if a virtual widget is present.
Proposal
Add a prop
isPersistent
, that if present will indicate that nothing should happen inside theclean
function.The text was updated successfully, but these errors were encountered: