Viewing profile — leebyron

The site is nearly all excerpts including the section with “practical advice” - those ten suggestions are nearly verbatim from the book author from the last chapter

I noticed a fair amount of complaints about this in the thread, so am sorry for the poor experience. In an attempt for simplicity I used a simple field which means it uses your OS …

Site creator here! Thanks to all who spent some time reading and scrolling through. I’m happy to see such great discussion here, and gives me some confidence the excerpts pulled we…

Great question. It applies to the variant of the spec as it exists today when the license was applied. Currently found at http://facebook.github.io/graphql/draft/ GraphQL's referen…

Whoa, awesome write up! This is a pretty good distillation of some differences, but I just wanted to reiterate that I'm more excited about the similarities. Having options for what…

Hi, Lee from the GraphQL/Relay team. To clarify a bit: we've removed fields from and changed our database schema repeatedly over the years. In fact we've migrated between entire da…

Hi, Lee from the GraphQL/Relay team here You're not off base at all! It's very similar to that. I think it's important to extract what was good and bad about this old website patte…

Hi, I'm Lee from the GraphQL/Relay team This technique of persisting the queries (and fragments) to the server at build time predates Relay - we've been using it on our iOS and And…

Hi, I'm Lee from the GraphQL/Relay team 1. Reactiflux Q&A is a great idea, perhaps someone who organizes that can help set that up. 2. We're a pretty small team and our primary foc…

There are many great libraries for backends available in many different languages. Some resources to find one: http://graphql.org/code/ https://github.com/chentsulin/awesome-graphq…

Awesome way to leverage the schema definition files to set up a super fast server. I see this being really useful for quick prototyping or for hackathons.

That theory is Facebook's practice. Four years later and we're on GraphQL API version 1. We add things which is safe, deprecate fields which we want to remove, and delete when hit …

Hey, author of Immutable.js here, You're definitely right to point out that Immutable.js is really not always what you want for small values that change all the time. Immutable.js …

GraphQL is designed for exactly this use case

Only if each field required loading a new row, and even then batching can be used to turn this back into one query. eg: { firstName, lastName } doesn't need to load new rows but { …

React and Relay are used to do this.

The GraphQL language syntax is useful because it naturally expresses more patterns than JSON can. However GraphQL is eventually parsed into an AST which is represented as JSON, it'…

In practice, it's actually pretty rare for a GraphQL schema (exposed to clients) to be identical to a database schema which often has admin-only columns or database-specific idiosy…

The libgraphqlparser project only provides C bindings for a GraphQL language parser but not an query runner or validator which often have differing APIs to feel natural in each lan…

Hey, original author here. The moral obligation is real, and I personally feel quite strongly about it and I know most of my coworkers feel the same. Morality is relevant because i…

New link: https://www.youtube.com/watch?v=WQLzZf34FJ8

They are attempting to solve similar problems: describing data needs on a client in a way that integrates well with how the data is used, and fulfilling those requirements efficien…

This is a great sum-up of a point I often find myself making a lot when explaining GraphQL. GraphQL is only capable of doing exactly what the server-side developer lets it. Order-b…

Perhaps that code is a bit misleading. The schema itself is defined and provided by the server. The idea being that a server would build up it's type definitions, and then call int…

Correct. SQL auto increment keys plus test accounts resulted in Zuck being 4.