Roll-for-Order Gameplay and Finite State Machine Cleanup

TLDR

Cleaned up state machine structure / logic and added “roll for order” functionality. Increased “test coverage” by writing additional script files to run against the REST API’s CLI tool.

Main work

• Added structure to the Player and GameState models to hold player joinOrder, which decides the player’s color during the game.
• Updating REST controller and CLI tool to accept new ROLL command.
• Continuing to refine the FSM implementation.

Challenges

• Continuing to make OOP design choices based on FSM progress. Difficult to decide which patterns are appropriate to avoid under/over engineering.

Learnings

• Because this is a solo project, I have been able to very cheeply fix / refactor some of my choices. For example, I made IState interface originally, but updated it to an abstract class for the introduction of “Free Transitions” from states. Free Transitions always require protected state enum and transition list variables for the FSM to coordinate correctly.
  • Jury is still out on if this is a good design choice.
  • Again, because this is a solo project, getting an MVP version of the entire game out and then refactoring is likely faster than agonizing over OOP choices or referencing Gang of Four for ideas.