There is no reason why it needs to be hardcoded and it can lead to problems if a region is configured but the AWS account the credentials are for has set up the resources in a different region.
Right now, there are buttons in game controller view to reset the reported and desired shadow, those buttons were added for testing proposes. With the same intention of testing the game by smoke testing, a reset admin shadow button should be added on that view. This way we can reset the admin shadow when needed with out the need of interrupt @Lenakh97 to reset it her manually.
Here we should use simulate the whole game process and make sure there are tests along the way that make sure that everything in the app runs smoothly, so that when we continue to improve the app we make sure that the general functions of the app is still working.
Display only angle and drive time input for selected robot. The selected robot should be selected when robot is clicked on, and unselected when clicked anywhere else on the field. Also selected when onPointerDown and unselect on onPointerUp.
Context: when players set the direction and press fight, admin sent the report and after that place the robots on correct position on fields, the desired rotation keeps on every click
When we move to the next round the angle line should be removed. Basically when clicking fight, the angle line should reset, be put to the center of the robot or just straight forward.
GameMaster name should be changed to Game Administrator, as this is a more gender neutral term + it makes more sense as we have called the page GameMaster page for Admin.
Default random positions for robots on admin page. The first time I used my own access key, the robots positions went crazy on the admin page for each update, randomly moving them everywhere, it was first when I selected the positions for the robots that they stood still until I moved them again. Some kind of default random set positions for the robots could be the solution.
Make a page in Gamecontroller where we can set reported and update the reported robots, so that we can simulate a game., this will eventually be used to create an automatic simulation of the entire game.
Right now there is not inner documentation that brings context on the reason why or the main concert of some variables and methods related to the movement of the robot.
In order to decrease the amount of time each person could invest in get the context and figure out the current status of the code, inner documentation should be addresses.
Display another name of the robot on the game page. Maybe also the users can create their own name? Also fix positioning of the robot name, either below or above