These are chat archives for jdubray/sam
to quote the GraphQL team:
GraphQL is unapologetically driven by the requirements of views and the front-end engineers that write them. […] A GraphQL query, on the other hand, returns exactly what a client asks for and no more.
This claim from the GraphQL team is simply fallacious:
Structured, Arbitrary Code: Query languages with field-level granularity have typically queried storage engines directly, such as SQL. GraphQL instead imposes a structure onto a server, and exposes fields that are backed by arbitrary code. This allows for both server-side flexibility and a uniform, powerful API across the entire surface area of an application.
So I would tend to disagree with that assessment:
i see the graphql layer more as a state function, than the model
If the model doesnt' exactly have what the client asks, you are out of luck
yes? as opposed to what?
I do believe that pushing (again) for the view to "query" something is setting us back 30 years.
What do you mean? The view has to send a query somehow to get the data, whether it's a REST/GraphQL API