Ports FetchDependencyGraph::toString() from JS. One difference: JS only displays the subgraph name, here I used the terse display for fetch dependency nodes, as subgraph name alone was not enough for the println debugging I was doing.
For OpPath, I don't think the JS side had an exact equivalent, it would just stringify the array directly which is equivalent to calling .toString() on all its elements and separating by commas.
The two op paths in this operation are displayed as:
userById(id: 1), name
userById(id: 1), email
The fetch dependency graph is displayed as:
[0] accounts[{}] <-
(The {} is a bug because we are missing the implementation for addAtPath: once implemented, the output would be [0] accounts[{ userById(id: 1) { name email } }].)
Ports
FetchDependencyGraph::toString()from JS. One difference: JS only displays the subgraph name, here I used the terse display for fetch dependency nodes, as subgraph name alone was not enough for the println debugging I was doing.For
OpPath, I don't think the JS side had an exact equivalent, it would just stringify the array directly which is equivalent to calling.toString()on all its elements and separating by commas.For this test query:
The two op paths in this operation are displayed as:
The fetch dependency graph is displayed as:
(The
{}is a bug because we are missing the implementation foraddAtPath: once implemented, the output would be[0] accounts[{ userById(id: 1) { name email } }].)