I don't agree with the first example, why would you not write an endpoint that returns all 3 of these sets of data if you knew it's what you required?
I believe this is misleading, to make GraphQL look more convenient when actually you can achieve the same extremely easily in REST with good planning.
Are you sure you want to hide this comment? It will become hidden in your post, but will still be visible via the comment's permalink.
Hide child comments as well
Confirm
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I don't agree with the first example, why would you not write an endpoint that returns all 3 of these sets of data if you knew it's what you required?
I believe this is misleading, to make GraphQL look more convenient when actually you can achieve the same extremely easily in REST with good planning.