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
I built a server using GraphQL.AspNet and a client using graphql-platform, but subscriptions do not work.
The issue seems to be caused by the ConnectionAck message being sent like this:
{"id":null,"type":"connection_ack"}
I opened PR #8224 in the graphql-platform repository, but the maintainer pointed out that according to the graphql-ws protocol specification, the id field must not be null in a connection_ack message.
I'm not sure which behavior is correct or which side (server or client) should be fixed, so I'm opening this issue for clarification.