3 ms·
I never got the edges and nodes thing, and every time I have worked with a graphql endpoint that did, I was indeed very annoyed. Feels like something that came
by ericwooley 5y ago
I never got the edges and nodes thing, and every time I have worked with a graphql endpoint that did, I was indeed very annoyed.
Feels like something that came with a graph database, and people tried to blindly copy it.
Graphql code generator is great though. Absolutely wonderful. Makes it really hard to go back to rest.
- hirundo 5y agoWe left out edges and nodes from our GraphQL API because of how confusing they are. But the downside is that we had to add a <collection>Stats object for each collection type to support meta data like the count. Still it seems to be easier this way for non-developers to learn. And the API consumers are mostly not developers, like account managers and accountants, usually via GraphiQL.
- dustymcp 5y agoever tried swagger and nswag for client generation in rest it does the same thing but requires abit of a wire