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
Will it be possible customizing error handling in checkResultAndHandleErrors? Right now it handling errors with concating error messages and throwing locatedError based on orginal graphql module.
For example, for stitching locale and remote schemas I want to proxy errors to my React app to localize them later, but in such checkResultAndHandleErrors behavior I can't proxy them as they are.
The text was updated successfully, but these errors were encountered:
Will it be possible customizing error handling in
checkResultAndHandleErrors
? Right now it handling errors with concating error messages and throwinglocatedError
based on orginal graphql module.https://github.com/apollographql/graphql-tools/blob/master/src/stitching/errors.ts
between 79 and 88 locs.
For example, for stitching locale and remote schemas I want to proxy errors to my React app to localize them later, but in such
checkResultAndHandleErrors
behavior I can't proxy them as they are.The text was updated successfully, but these errors were encountered: