I guess its better to go with scaphold.io where people actually do reply thanks though.

Hey @praneybehl and @iki! Sorry for the delay! We're currently getting a lot of requests and work on rolling out a new version for the next batch of users of the early access program. We'll be in touch very soon!

schickling just replied to your pm thanks

General technical question

GraphQL does not seem to support destructuring of types, does it not?

e.g.

createBlog (...CreateBlog): Blog

otherwise I end up with:

createBlog (blog: CreateBlog): Blog

which requires that I make queries this way:

createBlog({
  blog: {
    name: "foo"
  }
})

instead of:

createBlog(name: "foo")

createBlog(name: "foo")

is exactly the way it works. have you checked out the available mutations and queries in the GraphiQL playground?

btw, which of the two versions you suggested is actually used in the schema is the responsibility of the server. as far as I know it is not part of the GraphQL spec

@nilan You misunderstood me.

createBlog (...CreateBlog): Blog

is throwing syntax error.

I am asking if there is a syntax to achieve this.

ah, gotcha. well, I am not aware of a GraphQL client for JS that behaves like you wish. which client are you currently using?

graphql-js

This is not supposed to be client specific. I am asking if the language itself defines an eqv. syntax.

I have asked the question here.

oh, ok. I believe the spec is pretty clear on the format of GraphQL queries and mutations. So I would guess that the answer to the question in the issue title is 'no'. However, I think it could be a nice feature of a specific GraphQL client, if it would support object destructuring.

a specific client is not supposed to augment the graphql language spec

if you want to express that all the properties of the user type are required for this mutation, you can specify all of them separately as required arguments. then you would be able to get rid of the outer user field

oh, now I see where I was confused. I thought you want to call the createUser mutation with a user object as parameter, and that would produce the error. but you get the error when defining the mutation. sorry for my confusion!

yup

change Name & E-Mail @ Profile

--- Name

Thanks @xerc. We're already on it!

wow, you guys have great support!

Hey there! Join us at this webinar w Kamil Kisiela, a team member of Apollo Stack next week http://www.meetup.com/AngularZone/events/233444689

I wanted to try the https://github.com/graphcool-examples/react-relay-todo-example but I am always getting this error. Any help? Uncaught Error: GraphQL validation error ``Cannot query field "viewer" on type "Query".`` in file

/Users/dev/Documents/code/react-relay-todo-example/src/queries/ViewerQueries.js

. Try updating your GraphQL schema if an argument/field/type was recently added. Steps I did: Cloning the git repo. Adding my project id to the package.json and to the src/app.js. In my graph.cool dashboard I have a ToDo model with complete and text as attributes

I also tried the instagram example before but faced the same error message (I created a Post model for that)

@orlando are you using the Simple or Relay endpoint?