When the server returns an error with an empty string message, GraphQLError.message becomes an object instead of a string

[koutaro-masaki]

Describe the bug

If the server returns an non-empty string as message

Response

CombinedError

If the server returns an empty string as message

Response

CombinedError

It is likely an issue with the condition within rehydrateGraphQlError. When error.message is an empty string, error.message is falsy, leading to return new GraphQLError(error as any) even though error has the structure of a GraphQLError.

Reproduction

https://github.com/koutaro-masaki/urql-issue-reproduction

Urql version

urql v4.1.0

Validations

• I can confirm that this is a bug report, and not a feature request, RFC, question, or discussion, for which GitHub Discussions should be used
• Read the docs.
• Follow our Code of Conduct