hello! I'm having some difficulties with getting a

FIELDS_CHANGE

request to query more than just

clientMutationId

and I'm going a little bonkers. I don't know if the problem is being caused because of my graphql schema or if I'm not requiring the right information on the client side. I'd love any help from someone who has managed to implement their own react/relay frontend and graphql/node backend!

(you can dm me!)

@carlpeaslee can you describe your problem/code a bit more? how does the mutation look like

hi, yes, I definitely can!

one thing you can do to check if the schema is good is to use GraphiQL

enter your endpoint here 😛

once second and I'll push this branch up to a sandbox

Hi! I’m unsure if this is a general question about graphql or for graph.cool, but i wonder how i can request an entry in a model in a way so it’s only visible for the user who created it ? Like user A create a post. User A wants to edit the post, goes to url:

posts/:id/edit

. But user B is an ass**** and he want’s to ruin the day for user A so he goes to

posts/:user-a-post-id/edit

, and here he should be met with 404 or something. So i need to send the token with the request so that only user A can make that request. Do you have any ideas or concepts on how to achieve this ?

Does anybody have a site using Graph.cool that's live? Curious about some production examples

@yannik not yet sorry

Anyone using graph.cool with react apps made with CRA? I'm specifically interested in if anyone's gotten around the heavy caching done in the webpack config: https://github.com/facebookincubator/create-react-app/issues/462#issuecomment-251405606

hey @emilrmoeller we are working on a really neat feature that allows you to handle situation like yours simple smile stay tuned!

Yes!!! Sounds awesome!

Thanks @nilan!

Hey @yannik! Sure, I'll DM you with a couple of production examples!

Hey @afgh. That's a really good point. We're currently working on a way making it a lot easier to use Graphcool with CRA!

Did somebody do a comparison between graph.cool & scaphold.io? I'm struggling with the choice. Scaphold advantages: - subscriptions - more intergations - analytics - better pricing - can work with teammaes in the console disadvantages: - buggy console UI graph.cool advantage: - better docs - better console - clearer roadmap and issue tracking, seems that move people using it Using the formal criteria the schaphold.io is a better choice, but subjectively, it seems that graph.cool will be a more stable solution in long term. The business models are the same, only implementation matters in this case. @nilan @schickling, I'm sure that you know more than I, can you shed light on this topic?

Really good question @nick.kozhukharenko! Thanks for your collected comparison information above. In general we're happy to tell you that we'll be rolling out most of these missing features over the next few weeks as well. Among them are subscriptions & an integration for Algolia. For us it is crucial to provide a stable solution to our customers and not to break people's apps when rolling out new features. Besides that another fundamental difference is that Scaphold seems to still be in a prototype stage as their service is built on a simple Node backend. That's also how we started out but quickly realised that this cannot scale into a stable solution so we've spent months on rewriting everything in Scala which runs at the heart of our service. I'd be happy to provide more information if helpful!

@nick.kozhukharenko for me the deal breaker for scaphold was that the console was buggy as hell which made everything else practically unusable.

@kitze yes, it’s. It Need reloading very ofter..

I got frustrated with CRA (everything was buried!) but LOVE Next.js and deployment with Now. That team is genius, creating React apps is now so much faster

And my apps are better since SSR and progressive loading is just taken care of automagically

Trying out GraphQL/Apollo Client integration this week, fingers crossed

That’s exciting @allpwrfulroot! I don’t have any experience with Next.js yet. Do you think you could write a blog post about your learnings integrating it with Apollo and Graphcool?

@yannik http://graphql.training uses graph.cool

@allpwrfulroot see https://github.com/graphql-training – that repo was a CRA, and using Apollo + Graphcool