devFC

Am I wrong for thinking GraphQL is how builds APIs today?

GraphQL as core (anyone can select just the data they need)
Then some default queries offered via one call as REST endpoints (just a wrapper over the GraphQL)

and then for typesafety and production use on the client side combine GraphQL with effect to get end to end typesafety and return type validation in something like

What am I missing / where does this go wrong? trying to open my mind on GraphQL

Am I wrong for thinking GraphQL is how builds APIs today?

GraphQL as core (anyone can select just the data they need)
Then some default queries offered via one call as REST endpoints (just a wrapper over the GraphQL)

and then for typesafety and production use on the client side combine GraphQL with effect to get end to end typesafety and return type validation in something like

What am I missing / where does this go wrong? trying to open my mind on GraphQL

https://gist.github.com/tim-smart/e10e4cbaeff35242d8352adead30bef9

Developer 🤓 build, develop and operate Farcaster solutions @ dtech.vision also love tech, decentralization, fitness and oldschool rap 😎

I’ve used it a lot as a consumer, and I’ve arrived at the conclusion that graphql is great when you want to open access to a bunch of data and enable joins, without worrying about permissions 

For mutations im still in favour of very deterministic and specialised endpoints