Apollo-client: Allow passing in an existing Redux store and pick which key in the store should be managed by Apollo

[stubailo]

[jbaxleyiii]

@stubailo this will require a partial rewrite to move the default store generated from createApolloStore to be a combined reducer where all apollo data will live under a specified key. I'm thinking nesting it under an apollo key makes the most sense.

In order to support a dynamic key, we will need that to be an input of the ApolloClient and passed to query manager (I think, still working through it).

As long as you don't see any troubles with this direction, I'll proceed!

[stubailo]

yeah that sounds great! It would be good if it was possible to just not pass in a store, in which case Apollo would make one for you. Basically having flexibility while having sane defaults.

[jbaxleyiii]

@stubailo yep! 100% still possible!

[stubailo]

Fixed by #81

[jbaxleyiii]

@stubailo this closes out our needs to get this into production :tada: :tada: I'll let you know when it's alive and working in our app!

[stubailo]

Dude, amazing! Let me know. Excited to see our first set of production bug reports 😄

Sounds like I should get those breaking API changes in today, so that you don't have to make random weird changes once you start using it: https://github.com/apollostack/apollo-client/issues/82

[gschmidt]

@jbaxleyiii Super exciting! It's great having you guys as a partner. I can't wait to hear how it goes.

[johnthepink]

@stubailo if you don't get them all in today, I'd be happy to help you finish next week before I start integrating.

[nakedcity]

Is this one implemented already?

[helfer]

Yes

[nakedcity]

@helfer How do you connect it? new ApolloClien({store: AnyInstanceOfTheReduxStore?})

[stubailo]

http://dev.apollodata.com/react/redux.html