Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Property

Type

Description

gameId

number

ID of game being updated . or the resulting game that was published

This would be automatically filled in based on the game number when generating/uploading games and would be used when using the (future) rescheduling function

round

number

Not 100% sure if this is still desired

isPublished

boolean

ScheduleTeam

Same as before, with additional properties:

...

  • Convert the current card design (of the info step) into individual steps in the modal

  • 🚩 Previous draft selection TBD. This is used to determine the round Need to add a previous round input so that the scheduler should continue from and is very importantcan continue schedules as usual

    • This already exists, but isn’t exposed in the UI

    • Critical for PCAHA. Need to check if it’s feasible for their schedulers to use this instead of selecting the last league, or if we need to infer from DraftGames

  • Order matters in team selection. May be best to just maintain an order on ScheduleTeam directly so it can be easily reused. Otherwise, the teams step just duplicates the schedule’s teams tab

...

  • No longer necessary. Schedulers will be able to create draft games directly in the schedule

  • 🚩 The only config this flow needed was a starting number, how do we maintain this functionality?

Updates

  • 🚩 Drafts update existing games using their game number, how do we show this? When creating a game with a game number, do we automatically link it to a matching game to show what’s being updated?
    • Add starting number to schedule settings?

Updates

  • When a DraftGame is created, search for an existing game the schedule by number and link the gameId automatically

  • This will become relevant later when reusing this functionality for game change requests

...