GraphQL Working Draft

#1

Post by samhoggnz » Thu, Jul 02, 2015, 11:18 AM UTC

GraphQL Working Draft
facebook.github.io

Re: GraphQL Working Draft

#2

Post by hartror » Thu, Jul 02, 2015, 11:31 AM UTC

Some background: https://facebook.github.io/react/blog/2015/05/01/graphql-int...

Re: GraphQL Working Draft

#3

Post by AdamCraven » Thu, Jul 02, 2015, 11:45 AM UTC

hartror wrote: post #2

Some background: https://facebook.github.io/react/blog/2015/05/01/graphql-int...

With a talk from earlier this year that describes an implementation: https://facebook.github.io/react/blog/2015/02/20/introducing...

Re: GraphQL Working Draft

#4

Post by binarymax » Thu, Jul 02, 2015, 11:50 AM UTC

Why not have the query in JSON? Now you need a new parser.

EDIT: Thanks for all the replies, all of them very good points, and clearly show that JSON is not the most elegant option for a complex DSL.

Re: GraphQL Working Draft

#5

Post by colinramsay » Thu, Jul 02, 2015, 11:56 AM UTC

binarymax wrote: post #4

Why not have the query in JSON? Now you need a new parser. EDIT: Thanks for all the replies, all of them very good points, and clearly show that JSON is not the most elegant option for a complex DSL.

There are certain things that are a bit more elegant if you can have a custom query language. One example:

        query UseFragment {
          luke: human(id: "1000") {
            ...HumanFragment
          }
          leia: human(id: "1003") {
            ...HumanFragment
          }
        }
        fragment HumanFragment on Human {
          name
          homePlanet
        }

You could definitely have some JSON to represent this but it might turn out to be more trouble than it's worth...

Re: GraphQL Working Draft

#6

Post by andreasklinger » Thu, Jul 02, 2015, 11:58 AM UTC

binarymax wrote: post #4

Why not have the query in JSON? Now you need a new parser. EDIT: Thanks for all the replies, all of them very good points, and clearly show that JSON is not the most elegant option for a complex DSL.

the query contains by far more logic than should be put into json

you could map it to json - but technically you could map everything to json - doesnt mean you decrease complexity

the parser is the lowest problem of parsing and optimizing those queries i'd assume

Re: GraphQL Working Draft

#7

Post by monk_e_boy » Thu, Jul 02, 2015, 11:59 AM UTC

binarymax wrote: post #4

Why not have the query in JSON? Now you need a new parser. EDIT: Thanks for all the replies, all of them very good points, and clearly show that JSON is not the most elegant option for a complex DSL.

Readability I guess. The new syntax looks pretty good to me. A little heavy on the (( and )) but very obvious as to what is being asked.

Re: GraphQL Working Draft

#8

Post by vjeux » Thu, Jul 02, 2015, 12:04 PM UTC

Lee Byron is talking about it at React Europe right now, here's the live stream (which supports play back): https://www.youtube.com/watch?v=UclvvqNtNNo

Re: GraphQL Working Draft

#9

Post by seivan » Thu, Jul 02, 2015, 12:04 PM UTC

binarymax wrote: post #4

Why not have the query in JSON? Now you need a new parser. EDIT: Thanks for all the replies, all of them very good points, and clearly show that JSON is not the most elegant option for a complex DSL.

I'm guessing you might want some 'small' parts of logic, like the unary operation. Guessing!

Re: GraphQL Working Draft

#10

Post by Murkin » Thu, Jul 02, 2015, 12:05 PM UTC

There was a comment on the original blog post that while they (Facebook) use GraphQL they still fall back to Flux for some of the data handling.

Was this solved ? Did they manage to handle all the data needs of their apps with GraphQL or is it still limited to certain areas ?