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
This is a feature request for supporting automatical merging of multiple fragments with same field and typeCondition.
Transform
consttransforms=[newReplaceFieldWithFragment(subSchema,[{field: `fullname`,fragment: `fragment UserName on User { name }`,},{field: `fullname`,fragment: `fragment UserSurname on User { surname }`,},]),]
This happens due to default overwriting of the fragments instead of collecting them.
Use cases
GraphQL Binding - this would enable overlapping fragmentReplacements which have to be handled manually at the moment.
GraphQL Middleware - this would enable fragments support in graphql-middleware where we need support for a list of different fragmentsReplacements extracted from different middleware.
The text was updated successfully, but these errors were encountered:
ghost
added
the
feature
New addition or enhancement to existing solutions
label
Jul 17, 2018
Hello 👋,
This is a feature request for supporting automatical merging of multiple fragments with same
field
andtypeCondition
.Transform
Expected behaviour
Actual Behaviour
Use cases
GraphQL Binding
- this would enable overlappingfragmentReplacements
which have to be handled manually at the moment.GraphQL Middleware
- this would enablefragments
support ingraphql-middleware
where we need support for a list of differentfragmentsReplacements
extracted from different middleware.The text was updated successfully, but these errors were encountered: