You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Apr 7, 2020. It is now read-only.
We need to add a database to store each game and its current state so that it can be loaded again.
In addition, we want to be able to keep track of every turn that has happened. There needs to be a "Turn History" (list) in the user interface that describes what happened during that turn. Clicking on a previous Turn in the History List will ask the user if they want revert back to that turn's board state.
The actual database provider can be anything you like (SQL-based, NoSQL).
This exercise is intentionally open-ended to allow the code contributor freedom to implement a sensible solution. That being said, if you have any clarifying questions, you can contact ed@socialtables.com
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
We need to add a database to store each game and its current state so that it can be loaded again.
In addition, we want to be able to keep track of every turn that has happened. There needs to be a "Turn History" (list) in the user interface that describes what happened during that turn. Clicking on a previous Turn in the History List will ask the user if they want revert back to that turn's board state.
The actual database provider can be anything you like (SQL-based, NoSQL).
This exercise is intentionally open-ended to allow the code contributor freedom to implement a sensible solution. That being said, if you have any clarifying questions, you can contact ed@socialtables.com
The text was updated successfully, but these errors were encountered: