When constructing messages to seend to a peer using y-websocket, the constants used to identify the type of message must be re-defined when the message is constructed because they're not exported from y-websocket.
We can see this issue in the sample server in this same repo. The values are redifined here. Best to have a single source of truth and use values exported by the library.
dmonad
commented
2 years ago
When constructing messages to seend to a peer using y-websocket, the constants used to identify the type of message must be re-defined when the message is constructed because they're not exported from y-websocket.
We can see this issue in the sample server in this same repo. The values are redifined here. Best to have a single source of truth and use values exported by the library.
Huly®: YJS-752