2 ms·
"author" would be the same as in the REST endpoint. So for example a string. As for your question, why the user can't change the query (in this example) : beca
by valenterry 6y ago
"author" would be the same as in the REST endpoint. So for example a string.
As for your question, why the user can't change the query (in this example) : because it violates the specifiction and will be rejected by the server.
Does it answer your questions?
- dmitriid 6y agoSo, you're basically proposing to create a poor imitation of REST. What's the point of GraphQL in this case?
- valenterry 6y agoI suggest you to take a step back and re-read the thread. Maybe the context got lost. I replied to the following post: > https://news.ycombinator.com/item?id=25432655 https://news.ycombinator.com/item?id=25432655 In particular: > Its much harder to make an efficient resolver than it is making an efficient REST endpoint. As I showed, the claim is not true because it can be solved in the same way in both GraphQL and REST.
- dmitriid 6y ago> I suggest you to take a step back and re-read the thread. Maybe the context got lost. I've read the thread. And no, the context wasn't lost. The whole point of GraphQL is flexible queries. And it is harder to make an efficient resolver in GraphQL than it is in REST. And yes, your solution (and the solution everyone ends up arriving at) is reimplementing REST in GraphQL, poorly. Precisely because it is much harder to make an efficient resolver in GraphQL.
- valenterry 6y agoI think I have proven my point and I'm not eager to discuss additional topics about GraphQL in this subthread.