Use this.ctx.storage to store session data

[threepointone]

(instead of connection.state)

[third774]

Hope you don't mind — I threw up a commit that I think gets this into working order the way we want. Now that room state is derived from the session storage we can't rely on connection.send() throwing errors to remove users from the room state.

The other change I made was that I noticed we were calling JSON.stringify in some cases, but not in others when setting the user state.

this.ctx.storage.put(`session-${connection.id}`, JSON.stringify(user))

I went ahead and removed this since DO storage accepts structured clone compatible data types.

I deployed this change, joined a meeting in a couple tabs, and did another deployment, and the desired outcome was achieved: the room state did not change while the durable object restarted and the WebSocket connections reconnected successfully.

[threepointone]

good catch, I really need to land the new linting rules, I'll do so next week

[threepointone]

looks good! feel free to review and land this whenever you feel like it