Guaranteeing backward compatibility #7138
Unanswered
AndreaCrotti
asked this question in
Q&A
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
We have set up a graphql-mesh that fetches data from different internal graphql servers.
However it's not uncommon that we have the same type defined in multiple places, with slightly different definitions (extra fields or different required/optionals).
That actually caused a production issue since graphql-mesh merged the things as well as it could I guess, but broke the backward compatibility of the graphql query that it's now proxying.
What's a good way to make sure that does not happen again?
We'll add more API level tests, but ideally this should really be caught a lot earlier than that, even when you just build the mesh with
yarn mesh build
for example.Are there any tools/suggestions about how to do that?
Beta Was this translation helpful? Give feedback.
All reactions