2 ms·
> * Because of this, the actual GraphQL servers get less attention and there's less resources on building them. By graphql servers do you mean graphql clients
by masklinn 8y ago
> * Because of this, the actual GraphQL servers get less attention and there's less resources on building them.
By graphql servers do you mean graphql clients on the server?
I'd think there's not much resources on building them because the basics are so trivial, the composition features are rarely necessary so all you need is the ability to POST a query, and parse the resulting JSON document.
My experience of interacting with the Github v4 API was understanding how to make queries:
requests.post('https://api.github.com/graphql', json={
'query': query_string,
'variables': my_vars,
})
and then spending some time with the graphql explorer to know what "query_string" should actually be.
And then some code afterwards to check for errors and pull out the bits into "native" objects, but that would be no different in an other API style.