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
At the moment if you declare a field in a type and then compose it under an interface the interface will automatically expose all of the fields that appear in all implementations of the interface. There are however cases where this is not desirable behavior. Consider for instance a federated graph where different subgraphs expose different implementations of the interface:
Since each subgraph would not know about the implementations within the other graphs it would have no way of knowing which fields can be safely exposed.
I know magnolia doesn't support resolution of the fields within a scala interface, but we can probably go the other way and exclude them from an interface (perhaps even a specific interface?) by using an annotation like GQLExcludeInterface to mark a field as not visible to the interface.
The text was updated successfully, but these errors were encountered:
At the moment if you declare a field in a type and then compose it under an interface the interface will automatically expose all of the fields that appear in all implementations of the interface. There are however cases where this is not desirable behavior. Consider for instance a federated graph where different subgraphs expose different implementations of the interface:
Since each subgraph would not know about the implementations within the other graphs it would have no way of knowing which fields can be safely exposed.
I know magnolia doesn't support resolution of the fields within a scala interface, but we can probably go the other way and exclude them from an interface (perhaps even a specific interface?) by using an annotation like
GQLExcludeInterface
to mark a field as not visible to the interface.The text was updated successfully, but these errors were encountered: