Lol - the code example seems to imply that Zuckerburg's user id is 4.
As a ruby programmer, my gut reaction was that this had something to do with bugs caused by the object id of `nil` being 4. But of course that's not the case :)
GraphQL Working Draft
51–60 of 71 posts
Re: GraphQL Working Draft
#52Finally! It's exciting to see a serious challenger to the cult of REST.
> cult of REST Is this a thing?
Re: GraphQL Working Draft
#53Why 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 believe Netflix's Falcor, which seems very similar to Relay, uses JSON.
Re: GraphQL Working Draft
#54Re: GraphQL Working Draft
#55Re: GraphQL Working Draft
#56Earlier quoted context omitted.
I believe Netflix's Falcor, which seems very similar to Relay, uses JSON.
Where in the world is Falcor? We keep hearing about it, we saw the presentation, but this is all we've got and it's nothing: https://github.com/michaelbpaulson/Falcor
Re: GraphQL Working Draft
#57Earlier quoted context omitted.
As a ruby programmer, my gut reaction was that this had something to do with bugs caused by the object id of `nil` being 4. But of course that's not the case :)
You need to upgrade your Ruby version. The object id of `nil` is 8 these days :)
Re: GraphQL Working Draft
#58> Built with spec-md
Re: GraphQL Working Draft
#59Re: GraphQL Working Draft
#60I've been looking forward to this! One question; it appears as though the types and schema are passed with every request (eg https://github.com/graphql/graphql-js/blob/master/src/graphq... ) -- I assume part of the reason for this is versioning/sharing the schema, but is it always external, does the server ever know the schema a priori -- what's the thinking around this design decision? (It's a plausible idea! I'm ju…