Stream: graphql
Topic: Mutation usefulness
Florian Briand (Nov 22 2019 at 11:33):
One of the "bigger" advantage of GraphQL, from my point of view, is the improvement of the "Developer eXperience", and in particular the fact that APIs become "typed" and "auto-documented".
And that's, I think, where it could be an advantage to specify basic CRUD operations (and maybe some other operations) as mutations, to give to developers the "typing"/"validation" ability.
Grahame Grieve (Nov 22 2019 at 12:30):
... but FHIR already has this, no? But I agree that I didn't talk about the graphQL schema
Florian Briand (Nov 22 2019 at 12:36):
But REST clients don't have the autocompletion ;) But yeah, we could build REST FHIR clients with this behaviour ;)
Grahame Grieve (Nov 22 2019 at 12:37):
schema! I don't think we need to build this
Florian Briand (Nov 23 2019 at 11:07):
It's just mater of developer experience. As with programming : the javascript String.localcompare function is fully documented, but it's nice when your IDE help you to remember the function's parameters and the schema of the third parameter "options"
But it was just a hint about the subject, I don't think it's a top-level priority need ;)
Last updated: Apr 12 2022 at 19:14 UTC
