Both the legacy graphql-ws
and the newer graphql-transport-ws
protocols are concerned with the processing of a handful of messages.
Our implementation of the newer protocol uses dataclasses to describe messages and their type
. They are very pleasant to work with and look like this:
However, our implementation of the legacy protocol uses TypedDict
to describe messages and separate constants for message types. In our case they are harder to work with.
We should refactor the legacy protocols message definitions and use dataclasses for them as well.
Pay now to fund the work behind this issue.
Get updates on progress being made.
Maintainer is rewarded once the issue is completed.
You're funding impactful open source efforts
You want to contribute to this effort
You want to get funding like this too