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
By default graphql-js has a max error limit of 100, when this is surpassed it will return 101 errors with the last one being an "abort" error that you have exceeded the error limit. The Swift code is expecting all errors that return to have source location information and when the "abort" error comes through it causes a precondition failure and the user does not get the useful error logs they should.
To resolve this we need to update the error handling in Swift to properly handle this "abort" error to ensure the user is always receiving the proper error logs to aid in debugging errors.
The text was updated successfully, but these errors were encountered:
By default graphql-js has a max error limit of 100, when this is surpassed it will return 101 errors with the last one being an "abort" error that you have exceeded the error limit. The Swift code is expecting all errors that return to have source location information and when the "abort" error comes through it causes a precondition failure and the user does not get the useful error logs they should.
To resolve this we need to update the error handling in Swift to properly handle this "abort" error to ensure the user is always receiving the proper error logs to aid in debugging errors.
The text was updated successfully, but these errors were encountered: