Union / fragments handling error in 0.0.17 about graphql HOT 8 CLOSED

Sorry, haven't had time yet to dig into this issue. The issue appeared together with gateway usage. I'll try to debug / trace the issue in more details this week

from graphql.

@JohnStarich mind taking a look at this? It must be related to your recent PR

from graphql.

Sure thing, I'll take a look. Feel free to assign me

from graphql.

Hey @obukhov, do you have a minimal example that exhibits the issue?

Edit: I see we have test cases that cover inline fragments, which I think covers Union spreads.
I added a new test locally for the below scenario and haven't seen issues (yet):

query {
	items {
		... on TypeA {
			name
		}
		... on TypeB {
			name
		}
	}
}

# ApplyFragments result:
{
	name
}

from graphql.

Hey @obukhov, any luck so far? If you have an example using the gateway, that'd be helpful too.

I'd be happy to fix an issue if present, just don't know what to look for yet 🙂

from graphql.

@obukhov or @AlecAivazis Any luck? I've been unable to reproduce the above issue.

from graphql.

@obukhov I'll go ahead and close for now since we haven't heard back in a while. Feel free to re-open when you find out more!

from graphql.

@obukhov I think I missed this in my first attempts because the tests skipped the introspection step, which contained the bug.

@sGy1980de found the problem and fixed it! 🎉

from graphql.