-
Notifications
You must be signed in to change notification settings - Fork 71
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
Strange behavior with fragments #186
Comments
@mvid Could you try these queries against the experimental endpoint |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We are seeing some strange behavior with null fields and fragments.
Here is an example:
And this is the query:
In this particular example, we expect to get two items in the top level
packages
response, and then the follow uppackages
to be empty. However, what we get are in the top levelpackages
is an array with two null values in it. However, when we expand fragment into the query like this:Then we get the expected response, two
Package
entities with emptypackages
arrays returned in them.Why is the response between a fragment and it's exact same fields different? Also, the double null response seems incorrect, maybe it is related to the null expansion issue in #80
Any thoughts?
The text was updated successfully, but these errors were encountered: