sbking/next-apollo

ApolloClient integration for Next.js

next-apollo's Issues

Create an example directory

In addition to documentation, an example application is always helpful.

reduxRootKey vs reduxRootSelector

I'm having an issue with the reduxRootKey, which is being deprecated in favor of reduxRootSelector. This opens up the possibility of using arbitrary structures such as Immutable.js to hold your Redux state. Unfortunately, it also means that we have to know how the user is creating the state. Right now, only plain object states are supported. Perhaps in the future, we could add a way for the user to declare how their initial state should be constructed, as well as how it should be serialized and deserialized so the HOC can transfer the state successfully from getInitialProps on the server to the component constructor where it can be rehydrated on the browser.

Defaults?

Totally dig this approach! I’m wondering, is it worth providing some defaults (with the option to override those defaults) for those developers who might want to get going with Apollo and Next right away? Removing the requirement of creating 3 new files (initClient, initStore, and apolloFactory) after installing the package would reduce "scaffolding friction". It'd be cool if all a developer had to provide was a graphql endpoint to the library to get started, while still providing the option to override those individual files.

What do you think?