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
As you can see in the below query, i am requesting list of orders, each order has federated query with Branch, not all orders have a branch hence when the branch id is null, wundergraph returned mixed data, basically in the response you will see for each order record responses are correct until it reach the first null branch and it will start mixing data
---------------------------------------------federated query
branch service query as you see the problem is in {"__typename":"Branch"} basically it request with no id on go-tools it requests with {"id":null,"__typename":"Branch"}, i dont believe this should be request, and wondergraph should not expect other than graph, I tried same scnario on appolo and it does not request null id:
I tried the same thing on the apollo server and in the service query it neither asks for null id or leaves empty and it does not expect it
currently on wundergraph it sends it without an id and when the service replies with null, wundergraph starts mixing data
on go tools it sends with id = null and returns from service is null and go tools gateway starts mixing data.
WunderGraph information
wunderctl version : 0.111.2
Environment & setup
OS: [CentOS]
Database: [My sql ]
WunderCtl Version
wunderctl version : 0.111.2
The text was updated successfully, but these errors were encountered:
Bug description
As you can see in the below query, i am requesting list of orders, each order has federated query with Branch, not all orders have a branch hence when the branch id is null, wundergraph returned mixed data, basically in the response you will see for each order record responses are correct until it reach the first null branch and it will start mixing data
Variables:
---------------------------------------------federated query
branch service query as you see the problem is in {"__typename":"Branch"} basically it request with no id on go-tools it requests with {"id":null,"__typename":"Branch"}, i dont believe this should be request, and wondergraph should not expect other than graph, I tried same scnario on appolo and it does not request null id:
Query
Variables
federated response :
-----------------------------------Response-----------------------------------
How to reproduce
Expected behavior
I tried the same thing on the apollo server and in the service query it neither asks for null id or leaves empty and it does not expect it
currently on wundergraph it sends it without an id and when the service replies with null, wundergraph starts mixing data
on go tools it sends with id = null and returns from service is null and go tools gateway starts mixing data.
WunderGraph information
wunderctl version : 0.111.2
Environment & setup
WunderCtl Version
The text was updated successfully, but these errors were encountered: