Explain it to me like I'm five!
What's are they and why do you need them when working with graphQL?
Explain it to me like I'm five!
What's are they and why do you need them when working with graphQL?
For further actions, you may consider blocking this person and/or reporting abuse
Tony -
Ali Raslan -
guigoncalves -
choco -
Once suspended, davidwells will not be able to comment or publish posts until their suspension is removed.
Once unsuspended, davidwells will be able to comment and publish posts again.
Once unpublished, all posts by davidwells will become hidden and only accessible to themselves.
If davidwells is not suspended, they can still re-publish their posts from their dashboard.
Once unpublished, this post will become invisible to the public and only accessible to David Wells.
They can still re-publish the post if they are not suspended.
Thanks for keeping DEV Community safe. Here is what you can do to flag davidwells:
Unflagging davidwells will restore default visibility to their posts.
Top comments (1)
Schema stitching is about merging two different GraphQL endpoints into one by just introspecting the two schemas and figuring out the new schema. What's also possible is that we can now create links between those two schemas so the new resulting schema will work seamlessly with both of them without exposing the difference to the client.
This is a very good example of how that will work.
At first, GraphQL was born to allow you to aggregate other APIs into one. As more people started to expose GraphQL APIs of their own, there is now the need to aggregate these APIs and a single GraphQL makes total sense.
You don't need them though unless you need to aggregate other GraphQL APIs.
Refs: