Hello Graphcool :slightly_smiling_face: After som...
# prisma-whats-new
h
Hello Graphcool 🙂 After some frustration using existing tools (well, Next.js especially), I managed to create a decent starter kit for React-Apollo projects using Graphcool! Right now it supports authentication with both Auth0-lock and Auth0-js, subscription (without authentication token) and soon a better error logging system. Here it is : https://github.com/THook/react-apollo-graphcool-auth0-starter, feel free to use it for your next projet. I'll also make some improvements this week 🙂
💯 2
n
@hvillain Wooow, super awesome! You can share it in the forum so it doesn't get buried if you like https://www.graph.cool/forum/c/resources
minor nitpick, Graphcool is not in beta 🎂
s
could you share your issues with next.js?
h
ahah @nilan sorry about that one 😛 As I said, I need to write a decent README ahah. What I meant is that Graphcool doesn't support multiple endpoints yet, so we need to sync multiple endpoints in the client (with Redux) 😉
n
Hm can you elaborate on that one?
aren't you talking about Apollo Client here?
h
For example, I need to handle my Algolia calls separately, therefore using my own Redux store. Ideally, Graphcool could create an endpoint internally : I would still hit my Graphcool endpoint but you would handle to database to call. I may be totally mistaken on that one, but I thought one of the advantages of Graphql is that you can manage a single endpoint for every of your databases, no regard to what db your request will hit on
n
Ahh I see. Yea that's definitely something that we're taking a closer look at. However, as you mentioned the Algolia example specifically, in this case it probably makes more sense to communicate to Algolia's servers directly. That's also the recommended practice by Algolia: https://www.algolia.com/doc/faq/searching/searching-from-the-front-end-or-the-back-end/