Cancel game

[jimenezj8]

Make a command, /cancel_game, which will allow a user to select a game by ID, and cancel a scheduled game.

This slash command will fail if the game has already started. If a game starts with less than 2 participants, the game will auto-cancel. All associated rounds will be deleted.

• [x] Create slash command in Slack App portal
• [x] Create command handler for slash command
  • [x] Deny "cancel" request if game started already
  • [x] #16
• [x] Modify "Game" table model
  • [x] Add Boolean column "canceled" (non-nullable)
  • [x] Add VarChar column "announcement_message_id" (nullable)
• [x] Modify "Round" table model
  • [x] Add Boolean column "canceled" (non-nullable)
  • [x] Add VarChar column "announcement_message_id" (nullable)
• [x] Create method db_utils.py: cancel_game
  • [x] Takes game_id
  • [x] Marks associated game.canceled value TRUE
  • [x] Retrieve associated game.announcement_message_id
  • [x] Marks associated game.announcement_message_id NULL
  • [x] Calls db_utils.py: cancel_rounds with game_id
  • [x] Returns list[str] containing the associated message IDs, if any, for both Game and Round announcements
• [x] Create method db_utils.py: cancel_rounds
  • [x] Takes game_id
  • [x] Marks all associated round.canceled records TRUE
  • [x] Retrieve all associated round.announcement_message_id records
  • [x] Marks all associated round.announcement_message_id records NULL
  • [x] Returns list[str] containing associated message IDs, if any
• [x] Create method db_utils.py: update_game_announcement_message_id
  • [x] Takes:
  • game_id: int
  • message_id: str
  • [x] Updates Game record with the announcement message ID
• [x] Associate scheduled message with Game in DB
  • [x] Assign SlackResponse to variable for scheduled announcement message
  • [x] Retrieve message ID and store using db_utils.py: update_game_announcement_message_id
• [x] Before posting game announcements, check if there are players signed up (modify game_start_handler)
  • [x] Accepts:
  • Message text
  • Message metadata
  • Channel
  • Client
  • Logger
  • [x] Uses game_id in message metadata to check participants
  • [x] If > 1 participants, calls chat.postMessage with message text and metadata to channel
  • [x] Else, calls db_utils.py: cancel_game
• [x] #17

[jimenezj8]

Use this API method to get all currently scheduled messages

Use this API method to delete a particular scheduled message

[jimenezj8]

If I'm using a scheduled message as the action trigger...I probably don't need to store the scheduled message IDs unless I pre-schedule all the messages

I'm going to revert all the pieces that have to do with the message IDs