now saved on page refresh.
The game state is stored on the server and when the user refreshes
the page the game state is fetched from the server on socket
re-connection
Next step:
stop user from making any move when the use is viewing past moves
Socket connection re-implemented. Everything is working fine now.
All thats left to do is to make the app robust and handle some edge cases.
TODO
- The friends list is maybe hardcoded or whatever I dont know, but the problem is
it shows the same username no matter who the signed in user is. I need to fix that.
- Whenever the pawn reaches to tha last square for promotion an 'Invalid move' error is
thrown by the Chess class. Need to fix that too.
- Need to disable the chessboard (so user cannot make any moves) until the opponent has joined the game.
- Set timers for the game.
- Need to show the loading states in various places in the app.
- Improve the backend such that a user cannot create more than one room at a time.
- Remove hardcoded values from various places.
- Make the app responsive. The UI is good on desktop but it is very bad on mobile.
- Add a feature to search and add friends.
- Destroying the rooms when the match ends and set timers for auto destruction after a certain time.
- Need some logic to save games in the history.
- Add some tests.
sent to the user and allow the user to accept or decline it.
TODO:
- Add API for fetching challenges.
- Implement onClick for Decline button in Challenges component
New algorithm:
- User sends a request to create a room in the backend
- roomID is generated in the backend
- server responds with a roomID
- user stores it in the localStorage and is redirected to the game page
Changes made in this commit
Previously there was no api endpoint for room creation. Now the API is
utilized by the ChallengeFriend.jsx component as per the above algorithm
Moon Patel