John Resig: Introducing the GraphQL Guide
Hate to complain about GraphQL in general and not specifically this guide but I ran into to major issues with it and really wanted to like it but ultimately gave up on it until they fix some core issues.<p>I don&#x27;t see how I can implement complex object hierarchies that are not rigid. Only list is supported as an unbounded data type and for some reason there is no unbounded map&#x2F;dictionary data type even with simple restrictions like requiring string key type.  There is not even good advice on what key&#x2F;value pair naming convention should be for all languages.  The other is that there is very poor support for more general include&#x2F;exclude&#x2F;where filters.  The idea being arbitrary complex join&#x2F;filter clauses to function like sql statement with multiple joins and where clauses.  Have to rely on implementation specific conventions like what sequelize does to get that but not for arbitrary object graphs. Solve some of this and it might actually become as powerful as it is frequently claimed to be.