|
|
|
|
|
|
by riffraff
3161 days ago
|
|
|
> Why am I using a new query language if it's going to end up being exactly the same as the old rest query environment? the client controls the APIs without you touching them.
It is required that the client syncs up with the server but you don't have to touch backend code to change the set of fields you want (this works for internal clients, not open APIs, clearly). If you're thinking "but I can just allow the client to select fields in my JSONAPI compliant endpoint", yes, you can, and when you add includes for nested fields, and nested selections, you basically get 90% of graphql :) |
|
|
True, but until someone provides a great software kit for doing that work, I'm not going to allow arbitrary extensions.