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

Vadliate service schemas when merging #53

Open
AlecAivazis opened this issue Jan 30, 2019 · 0 comments
Open

Vadliate service schemas when merging #53

AlecAivazis opened this issue Jan 30, 2019 · 0 comments
Labels
enhancement New feature or request merging schemas

Comments

@AlecAivazis
Copy link
Member

AlecAivazis commented Jan 30, 2019 •
edited

In order to function, we need each service to obey a few rules:

  • Each service must satisfy the global ID spec
  • Boundary types must implement Node in every service
  • Boundary interfaces must be supersets of Node
  • Types referred to in gateway fields need to implement Node
@AlecAivazis AlecAivazis added enhancement New feature or request merging schemas labels Jan 30, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement New feature or request merging schemas
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@AlecAivazis