Stitched schema errors are replaced with another one

[yaacovcr]

Stitched schema errors are replaced with another one

[yaacovCR]

Seems like you are stitching to remote schema with a different schema using transforms?

I think your transform needs to modify the error path so it can be properly recreated. Would you mind sharing the delegation and transform code?

Error proxying works by attempting to reconstruct a response even when null so multiple errors can be passed by gateway, all with correct paths.

[yaacovCR]

I am working on adding support for this to WrapType and ExtendSchema related transforms...

[chess777]

No, I'm not using transformation. This path comes from backend.

[yaacovCR]

Maybe you should be using a transform? I am not quite certain without seeing more code. Is there a reason that path does not match your schema?

[yaacovCR]

Actually, tests show already working for WrapType.

[yaacovCR]

Very interested in this. If you could share a detailed code sample, that would be amazing.

[chess777]

Ok, I understand. It seems I can't just add arbitrary path that does not correspond to schema for errors when stitching as this breaks error matching to properties.

[yaacovCR]

Correct, I believe this is as per spec: https://graphql.github.io/graphql-spec/draft/#sec-Errors

You should be able to add whatever you want to error under extensions key.

[chess777]

Thanks for help!
Your help is invaluable