-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update field collection to allow inline fragment without type #3384
Conversation
…he fragment type applies first and that this test only happens if there is a fragment type defined
bfff2f7
to
37acabd
Compare
Thanks! I'm extremely excited about the |
Odd that the Go 1.22 Integration / federation check failed, but the Go 1.23 did not. I'm assuming it's just flaky and not related to these changes, so that's annoying. (If anyone sees anything obvious, I would appreciate you telling me!) |
Hm, yeah, odd. I'll continue to look. Are there any changes / upates you'd like me to make to the example or any docs? Or any additional tests for collection? If not, I'll remove the draft description after trying to pinpoint the 1.22 failures. |
@StevenACoffman after a few more passes and some tests, I think this is just flaky due to a slow startup, associated with the calls out to
We aren't really pausing for some meaningful signal, so might just get out of sync if the system is running slowly. (I could not replicate it.) Are there any changes / updates you'd like me to make to the example or any docs? Or any additional tests for field collection? If not, I'll remove the draft description and hopefully the tests all pass when we trigger them again? 🤷 |
Thanks for looking at those flaky tests. It's annoying, but not this PR's concern. Currently, for I'm not going to hold up merging this PR for that now, as it's wasn't your changes that caused those to be uncovered, but I would gladly merge any later PR that added more test coverage for them if you get a chance. |
Yeah sure I'll do a follow up next week. |
Updates the algorithm for field collection to hew more closely to the version in the spec described in https://spec.graphql.org/June2018/#sec-Field-Collection. Specifically, it:
@include
and@skip
directives only after type application is performed (for inline and spread fragments).This issue was identified in relation to the use of
@defer
on an inline fragment without a type condition, as described in #1972 . Because@defer
is obscure and this was hard to recreate / test, this PR also adds an _example server that can handles deferred responses correctly.I am not sure if there should be any documentation updates related to this.
I have: