Validation handling inconsistent for queries vs. subsctiptions over graphql-transport-ws

[kristjanvalur]

Describe the Bug

A websocket connection can be used to perform queries as well as subscription. With subsciption schemas, a validation error results in a error message before the subscription commences. For query schemas, the same validation error results in a "next" message containing "errors" in its
ExecutionResult member.

This kind of different error handling is inconvenient. In the case of queries, it makes it harder to distinguish between a validation error and an error resulting from the query execution.

System Information

• Operating system:
• Strawberry version (if applicable):

Additional Context

I have created PR #3671 to illustrate the problem. It contains behavioural tests taken from a separate PR validation graphql-transport-ws based behaviour.

Upvote & Fund

• We're using Polar.sh so you can upvote and help fund this issue.
• We receive the funding once the issue is completed & confirmed by you.
• Thank you in advance for helping prioritize & fund our backlog.