3 ms·
I found both the discoverability and querying in GraphQL much better compared to Rest. Can you explain what you mean in more detail?
by valenterry 6y ago
I found both the discoverability and querying in GraphQL much better compared to Rest. Can you explain what you mean in more detail?
- benatkin 6y agoDiscoverability with GraphiQL and Intellisense aims to make it self-documenting. It doesn't work out that well and you wind up needing documentation anyway. Queries over GraphQL often wind up being handled by custom resolvers and being about the same as remote procedure calls. It is kind of neat how it separates the queries from the mutations. Blitz does that, but with GraphQL being optional: https://blitzjs.com/docs/query-resolvers https://blitzjs.com/docs/query-resolvers gRPC just provides an efficient transport and has the client library provide the interface. It works out pretty well for google APIs.
- valenterry 6y agoI agree that more comprehensive documentation is often necessary. But still, having GraphiQL that let's me discover all possible queries with their types and a small explanation for each field is a great win. I like that much better than for example generated swagger documentation. So how exactly is this a net loss? If anything it does not improve the situation - but making it worse?