If you've used JSON:API and GraphQL, what would you say are the key missing features in JSON:API? Conversely, what did you like better about JSON:API? (feel free to answer one or both questions)
-
-
Replying to @wycats
In my mind, they're isomorphic but tailored for different use cases. JSON:API has de-duping records in a response locked down. GraphQL makes writing "includes" easier for and promotes RPC style mutations.
1 reply 0 retweets 1 like -
The main differences I see are actually in the programming models of the clients for each style of API. In GraphQL, queries tend to be first class objects used as cache keys. In JSON:API you tend to cache by (type, id). (yeah, yeah Apollo does both)
1 reply 0 retweets 0 likes -
Anyways, to answer your question. I'd love if JSON:API had... - Types/schema/schema exploration as a first-class citizen - A nicer language for expressing includes - maaaaybe some conventions around RPC style APIs? I find new devs struggle to model things with REST
2 replies 0 retweets 2 likes -
What do you mean by struggling with rest? Do you have an example? When teaching I found most jrs understood traditional API GET/POST/PUT/PATCH/DELETE (I won’t say true “REST” since there’s more to that)
2 replies 0 retweets 0 likes
I think the issue is when you need to create synthetic resources to model verbs.
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.