-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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
Query variable definitions are dropped when used in a nested query #620
Comments
I've tried rolling back version by version and this issue was introduced in 0.4.12. |
@sambs oh, interesting. Thanks! Can you make a PR with a failing test for this? That would help getting it fixed faster. |
Hi there, Any idea when this would be resolved? While evaluating Apollo for our products, I encountered the same problem by trying to use parameters lower in the query tree (which is totally fine by GraphQL)...
This resulted in the issue that Apollo did only send query getLabels($account: String!) and omitted the $search param, which then resulted in an issue from the server saying that $search is not a defined as a variable... I have a workaround in place including a dummy "root" query that accepts all the variables that I might need. This works, but I don't think I need to tell you who dirty this feels ;) And I most certainly don't want to push this too production now...
Thanks and kind regards, |
@danielgriese We're going to remove query diffing pretty soon (timeframe: less than a week). I'll make sure we take care of this bug as well when we do. |
Should be fixed in |
It seems that if query variables are used in a nested way such as this:
...then they're dropped from the executed query which ends up looking like this:
The text was updated successfully, but these errors were encountered: