Norbert Dragán
Norbert Dragán
Every time a player sends `player_join` for the next hand, we receive back `balance: 200`. I suppose it's because joining the table is exactly the same as getting to the...
Currently, the timer function is implemented on the frontend with JavaScript. The problem is that if the JavaScript execution stops somehow on the client-side (eg. the user calls `alert()` from...
We will need a landing page that will display the available tables. Displaying the number of players on the table would be a nice to have, but it might entail...
@sg777#2257 there are two missing pieces for the Table Select feature to work: **1. The ability to check how many people are currently at the table _before_ joining the table**...
HTTPS is also more secure, and in order to go to production on the web, we would have to switch. I would like to use netlify for continous deployment, but...
Currently, we don't log what cards the board get populated with, or what each player's cards are at showdown. We should log these for more complete hand history experience. ###...
Currently, the audio always plays, no matter what. It can be muted via the browser, but it might not be the best user experience.
The window currently is set to be fixed at 800x600, to match the size of the table. For some reason, on @sg777's windows machine (see screenshot below) this size is...
The shape of the state object (defined in `initialState.tsx`) is getting a little bit out of control, it might be a good idea to refactor it. For example, we could...
The front-end originally started naming players with `1`, as `player1`. The backend however, starts counting from `0`, as `player0`. This is causing some unnecessary and sometimes confusing code all around...