chore: update GraphQL schema design: remove stitching, add query result unions #573
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
mzikherman
changed the title
joeyAghion
approved these changes
Jan 13, 2026
|
|
||
| You can read about how to build and test a stitched API | ||
| [via the blog](http://artsy.github.io/blog/2018/12/11/GraphQL-Stitching/). | ||
| We are moving away from schema stitching - backends should implement vanilla RESTful JSON API's, with data loaders in Metaphysics (typically mapping 1-1 with an API endpoint) responsible for fetching. |
Contributor
There was a problem hiding this comment.
Small update, but years of attempts and anguish!
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
artworkResult