Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Proposal for schema stitching at runtime - prevent links from getting added twice #5

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

mattblackdev
Copy link

This PR is part of a bigger effort discussed in the cult-of-coders/apollo repo. When I attempted to initialize the apollo package a second time at runtime Grapher throws because it will addLinks to collections that already have links. I hoping to learn the right way to do it via feedback to these PRs but I wanted to show some effort up front. Like a proof of concept.

My initial thoughts are that this is a very brittle check and links could be different in more way than the field.name. So looking for advice on a better way to "refresh" grapher with a new graphql schema.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant