@willotter Would be great if you could open an issue in https://github.com/graphcool/feature-requests/projects/1 to track this 🙂

Hi there! Quick dummy question as I'm all new to this. How can I set up my local environment to use an offline version of the schema/db?

Hey @xdamman! You can download the JSON representation of your GraphQL endpoint with

apollo-codegen

(See: http://dev.apollodata.com/ios/downloading-schema.html). Running your actual server offline isn't possible yet. What would be your use case?

@xdamman: then you don't want to use graphcool but you'd want your own graphql server (e.g the one of Apollo or plenty of others out there)? But I'm also interested to know your use case, for me I just use graphcool also for local dev so far. Just doesn't work in the plane 😛

Work in the plane was my use case. Also, for running tests on CircleCI you want to avoid having to do network calls. There should be an easy way to download the latest version of the database and import it locally.

@sdubois I'd still want to use GraphCool, in the same way that we were using MongoHQ (now Compose) to host our MongoDB databases for Storify.

@xdamman Yes the local DB for testing is important

But graphcool is much more than a DB, it hooks into aws lambda, authentication, etc

You maybe need to see graphcool as equivalent to opencollective-api as a whole

How do Firebase users solve this?

Hi everybody <!here|@here>. We are setting up a small group of early adopters who want to help us test new features before they are released. Currently we are testing subscriptions and advanced permissions. Let me know if you want to be included on the beta list!

@sorenbs would love to be included! just learned about graphcool today and am glad to try it out 😉

Excellent Austin - and welcome 🙂 Just send me a pm with your mail here or soren@graph.cool

@schickling: any thoughts on question above? https://graphcool.slack.com/archives/general/p1481392704000232

Hey @sdubois - this is similar for Firebase. Most people simply accept that they can only develop while online. A few people create mocks around the firebase data layer so they can develop and test locally. This is an area where we want to have a better story than Firebase, but we are still evaluating how best to solve this use case. If anybody has a really well developed idea of how they would like to Graphcool to fit into a workflow that includes local development, ci etc I would love to talk more 🙂 For now it is unlikely that we will have this implemented in the next 6 months.

Thanks @sorenbs /cc @xdamman

@sorenbs @sdubois one option is to build more advanced mocking functionality into

graphql-tools

so that you can download the schema and mock it locally

but it wouldn't be perfect

@sashko I think that would be an interesting first step. Have you had any talk about this at Apollo? Are you seeing demand?

well people heavily use mocking to mock their own production server

so I imagine it would work just as well for graphcool

(we use the mocking feature in optics exactly for this case - to avoid running production backend if we don't need to)

Yeah absolutely. Most people I talk to use mocking only for tests and do development on the frontend against a staging server running alongside the production servers. I was curious if you see the same thing or if people rather want to have a full backend running locally to develop against.

Hello. I'm working off an ejected create-react project, and using .graphqlrc and the react-relay plugin (via babel-plugin-react-relay)... I'm not actually doing anything with Relay in the app yet, but when I run my development server, I get

Error in ./src/index.js
Module build failed: TypeError: Cannot read property 'map' of undefined
    at Array.map (native)
    at Array.map (native)
 @ multi main

I'm able to separately resolve a schema from the server and send it to a son file, so the mechanics of graphqlrc are working fine. Any thoughts? It has some kinship to this: https://github.com/graphcool/babel-plugin-react-relay/issues/16, but maybe it's more babel specific in my context.

the error only occurs when including the react-relay plugin

Hey @zeeshanlakhani. Have you tried the following debugging tips? https://github.com/graphcool/babel-plugin-react-relay/issues/16#issuecomment-265110115

was about too

Would be great if you could give this a try so we can figure it out together 🙂

just wanted to see if there was a solution around what had happened, but sure