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)
-
-
Yep, building complex object graphs from something in ember is a pretty big ass pain. Typically I end up making a virtual model that consumes all of the attributes. It's certainly quite good for R, I'd love it if Ember Data was extracted just for it's request building features.
-
So something like sideposting and sidedeleting would scratch a major itch for you?
-
Yep, I believe its in the spec, but it's not supported by anyone.
-
It's not in the spec yet, but
@richmolj and@wadetandy are working on it! It's in their JSON:API Suite already, and I'd like to extract it back into the spec. Citation: https://jsonapi-suite.github.io/jsonapi_suite/ruby/writes/nested-writes … -
Ahh, we use jsonapi-resource.
-
Mutations solve this well. One of the things I like about gql is that separation between queries and mutations
-
Out of curiosity, what about the GQL separation between queries and mutations that you like better than in REST? Just the nested nature of the mutations or is the RPC style attractive on its own?
End of conversation
New conversation -
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.