-
-
Notifications
You must be signed in to change notification settings - Fork 3.4k
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
Update docs for using a different store key #1132
Comments
Yeah, we're still working on updating the docs for v6 (and hopefully setting up versioned docs for v5 vs v6). |
Out of curiosity, were you actually using that? If so, what was your use case? |
It's for a Chrome extension, and it grew out of some architectural particulars there. We have a main store in the background page of the extension that's the final source of truth for all user data. Our UI is a React app which can be inserted directly into pages as an iFrame, and there might be several instances of the UI inserted into different tabs at once. We use the excellent It can be confusing at times, but it has actually worked out rather well. |
Ah, interesting. Does the ability to supply a custom context instance in v6 still help for your use case? |
I haven't tried just yet, but I imagine it should be workable. I can create the context and pass it to the Does that sound right? EDIT: That's working! I created a null context called
And I wrapped the
Then when I want to connect a component to the local store, I just do So, in the end, very little change needed. |
createProvider
as deprecated/removed.storeKey
inconnectAdvanced()
as deprecated/removed.The text was updated successfully, but these errors were encountered: