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.

Sign up for GitHub

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

Jump to bottom

Spread unions across service boundaries #43

Open
AlecAivazis opened this issue Jan 22, 2019 · 1 comment
Open

Spread unions across service boundaries #43

AlecAivazis opened this issue Jan 22, 2019 · 1 comment
Labels
discussion

Comments

@AlecAivazis
Copy link
Member

AlecAivazis commented Jan 22, 2019 •
edited
Loading

We should explore if there is a reasonable story and motivation for allowing different services to contribute different members to the same union.

Related to #58
@AlecAivazis
Copy link
Member Author

AlecAivazis commented Jan 23, 2019 •
edited
Loading

If a union is spread across multiple services we can create a step that is inserted based on the value of __typeName. It's important that a node query does not end up at a service that does not have the underlying type defined as that will result in an error

@AlecAivazis AlecAivazis added enhancement New feature or request query planning labels Jan 27, 2019
@AlecAivazis AlecAivazis mentioned this issue Feb 9, 2019
Open
@AlecAivazis AlecAivazis removed the enhancement New feature or request label Feb 9, 2019
@AlecAivazis AlecAivazis mentioned this issue Aug 9, 2019
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
discussion
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@AlecAivazis