Yeah, my two simultaneous thoughts are “I don’t care what eccentricities exist in the API as long as I get good error messages, that’s the real primary concern” and “…but specific issues like the relationship between game/move and game/connect are things that are easier for me personally to make docs PR than having to onboard into the whole OSS codebase”
2 Likes
Here’s a weird one: sending the move "" results in a "game/:id/error" message, but not a [requestId, null, error] message. It makes me wonder what cases the request response will actually populate the error field.
1 Like