Update docs for using a different store key

• Mark createProvider as deprecated/removed.
• Mark storeKey in connectAdvanced() as deprecated/removed.
• It would also be nice to add a new section detailing how to accomplish it with the new API.

[markerikson]

Yeah, we’re still working on updating the docs for v6 (and hopefully setting up versioned docs for v5 vs v6).

[ethanroday]

I haven’t tried just yet, but I imagine it should be workable. I can create the context and pass it to the Provider at the app level, and then just call connect with the context option. (I’m basing this on the You may also pass a {context : MyContext} option to connect part of the error message.)

Does that sound right?

---

EDIT:

That’s working! I created a null context called LocalStoreContext and provided both stores at the app level:

 // index.ts
<Provider store={store}>
  <Provider store={localStore} context={LocalStoreContext}>
    <App />
  </Provider>
</Provider>

And I wrapped the connect() function like so (I was using storeKey before; now I’m using context):

// local-connect.ts
export const localConnect: Connect = (mapStateToProps?, mapDispatchToProps?, mergeProps?, options?) =>
connect(mapStateToProps, mapDispatchToProps, mergeProps, {...options, context: LocalStoreContext});

Then when I want to connect a component to the local store, I just do @localConnect( /* ... */ )(MyComponent) like I was already doing.

So, in the end, very little change needed.