Briefly, but clearly describe what you did, and explain any new code.
Oh boy, we did so much.
The gist is action cable is set up on both the front and back end
'actioncable.js' was used to connect to the back end
Each move is sent to the back end through a PATCH request. If the move is successful the board is updated through action cable and broadcasted out. Only successful moves are made.
In other words, the front end will never 'make' moves. Only valid moves sent through a fen from the backend are added to the board. The chess.js library validates the logic of the move before being sent, the back end validates that the respective player is on their turn and can move that piece.
What are the relevant tickets?
Closes #11
Bugs:
Are there any concerns, issues, or bugs in this branch? If so describe them.
Currently no bugs. It is on heroku and two players can test the game working
Checklist:
[x] I have performed a self-review of my own code
[ ] I have used tests to prove my fix is effective or that my feature works
[ ] New and existing unit tests pass locally with my change
This branch is deployed on heroku connected to the back end and two separate players can play chess at the same URL
Purpose:
What does this merge do? Check all that apply.
Description: What does this PR do?
Briefly, but clearly describe what you did, and explain any new code.
What are the relevant tickets?
Closes #11
Bugs:
Are there any concerns, issues, or bugs in this branch? If so describe them.
Checklist:
[x] I have performed a self-review of my own code
[ ] I have used tests to prove my fix is effective or that my feature works
[ ] New and existing unit tests pass locally with my change
This branch is deployed on heroku connected to the back end and two separate players can play chess at the same URL