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
Hi, I've found a gap in support for the legacy graphql-ws protocol. The spec indicates that for error messages the payload should be a single "Error" object, but currently Mercurius only adheres to the graphql-transport-ws protocol error format by always returning an array of GraphQL errors.
I realize that the graphql-ws protocol is considered deprecated, but given the docs state both are supported I think this is worth addressing. Thanks!
The text was updated successfully, but these errors were encountered:
Hi, I've found a gap in support for the legacy graphql-ws protocol. The spec indicates that for error messages the payload should be a single "Error" object, but currently Mercurius only adheres to the graphql-transport-ws protocol error format by always returning an array of GraphQL errors.
I realize that the graphql-ws protocol is considered deprecated, but given the docs state both are supported I think this is worth addressing. Thanks!
The text was updated successfully, but these errors were encountered: