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
When composing the schema there are no errors but the @private directive is completely ignored.
In the linked example, you can see that the resolvers for bar and barsByFoo should be private but instead they are still visible on the Gateway
Relevant log output
Additional context
No response
The text was updated successfully, but these errors were encountered:
Hey @michaelstaib, thanks for the link, the docs did not exist when I started looking at this 🙃 but useful to know.
I have read the docs, but the only mention I can find of the @internal directive is with respect to lookups.
Is there a way to prevent the gateway from exposing all of the subgraph query by default?
Product
Hot Chocolate
Version
14.1
Link to minimal reproduction
https://github.com/aidy-jenkins/FusionIssueReproduction/tree/private-directive
Steps to reproduce
Add the line
extend type Query @private
into a schema extension file when defining a subgraph.Pack and compose a gateway as normal and run it.
Check the resulting Gateway schema
What is expected?
The
@private
directive should be hiding all the types from theQuery
as per this blog post:https://chillicream.com/blog/2023/08/15/graphql-fusion
What is actually happening?
When composing the schema there are no errors but the
@private
directive is completely ignored.In the linked example, you can see that the resolvers for
bar
andbarsByFoo
should be private but instead they are still visible on the GatewayRelevant log output
Additional context
No response
The text was updated successfully, but these errors were encountered: