You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It is the same as #2662 but for single schema projects
To support this we need the following.
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?)
Schema filtering logic (we can probably re-use what we already have for federation subgraph filtering)
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
The text was updated successfully, but these errors were encountered:
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.
It is the same as #2662 but for single schema projects
To support this we need the following.
@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?)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
The text was updated successfully, but these errors were encountered: