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
{{ message }}
This repository was archived by the owner on May 16, 2019. It is now read-only.
The fragments work as expected when used independently, and if they operate on different nodes of data they both resolve.
Expected
Both fragment should be resolved and firstName and lastName returned. That's my understanding of the spec, and I ran a similar experiment against express-graphql and it merges correctly. This leads me to believe it's a bug within KGraphQL.
The text was updated successfully, but these errors were encountered:
Having an issue where fragments that operate on the same data node are not being merged, rather only the last fragment is being resolved.
Setup
A simple query resolves correctly
Result
But when multiple fragments are used that operate on
name
only the last is resolvedResult
The fragments work as expected when used independently, and if they operate on different nodes of data they both resolve.
Expected
Both fragment should be resolved and
firstName
andlastName
returned. That's my understanding of the spec, and I ran a similar experiment against express-graphql and it merges correctly. This leads me to believe it's a bug within KGraphQL.The text was updated successfully, but these errors were encountered: