Yaacov Rydzinski

First of all, thanks for contributing! We appreciate the effort to improve the library. There is also a lot of interesting ideas here with regard to order of execution, which...

Question: Does your nested mutation resolver do something different when included within a query operation? Like throw an error?

Awesome find, we tried to solve this with onLocatedError, but that logic is wrong as you have discovered. Fix in the works :)

I think what is actually happening is that all indices are of the first list element sent in

the simple fix I was thinking of turned out to be a dead end :( I am glad you found a workaround! Have to think more about how to fix...

One problem is these embedded errors can be deeply nested within the result, so to rewrite the paths, we would need to deeply traverse the result. we can’t simply rewrite...

I think the end solution is to remove the error embedding step from the batch function called by batchDelegateToSchema, and performing that manually after the data loader returns.

Very possible, but requires a new transform that maps values in schema and translates in request and result... PRs welcome

It is potentially tricky to modify enum values as when transforming results you do not have actual access to field type, because of aliasing When transforming the request, the request...

Would be nice to just generally have a function that takes a document and result and visits the data and errors with the type info.