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

support schema contracts for single schema projects #3856

Open
n1ru4l opened this issue Jan 23, 2024 · 1 comment
Open

support schema contracts for single schema projects #3856

n1ru4l opened this issue Jan 23, 2024 · 1 comment

Comments

@n1ru4l
Copy link
Collaborator

n1ru4l commented Jan 23, 2024

It is the same as #2662 but for single schema projects

To support this we need the following.

  1. Light "Specification" of @tag for single schema projects (maybe opt-in via settings, or should it be done similarly to federation schemas with a @link directive on the Schema object?)
  2. Schema filtering logic (we can probably re-use what we already have for federation subgraph filtering)
  3. A Proxy gateway for serving the contract schema in front of the "full graph"

The proxy gateway is optional from the Hive perspective, though we should have the full usage path covered for pleasant usage. For the latter conductor will do. See the-guild-org/conductor#436

@tandrup
Copy link

tandrup commented Feb 7, 2024

We have build our own custom schema transform to do basically schema contracts in our schema stitching based setup.
But would be nice to have it supported in GraphQL Hive. #3593 was partly because of these transformations.

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

No branches or pull requests

2 participants