I find this strange, because this has been a solved problem with graphql-js for about 18 months now, and provided as a core feature in other implementations suc

I find this strange, because this has been a solved problem with graphql-js for about 18 months now, and provided as a core feature in other implementations such as Sangria in Scala. I've written about this particular problem, calling out solutions that exist in different languages: https://dev-blog.apollodata.com/optimizing-your-graphql-request-waterfalls-7c3f3360b051?source=linkShare-913ef66da585-1492188730 https://dev-blog.apollodata.com/optimizing-your-graphql-requ...