...
The current schedule info step is split into multiple steps for matchups and scheduling in the modal
Starting game number input would is no longer be necessary as we would use game numbering sequences insteaddrafts will not use a sequence until the games are published
Need to add a previous round input so that the scheduler can continue schedules as usual
This already exists, but isn’t exposed in the UI. It’s automatically populated based on the “previous draft” input, so this will be replaced with a previous round input.
🚩 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
ScheduleTeams are now the source for generating the schedule, replacing the teams step
Order matters in team selection. An order will be added on ScheduleTeams so it can be easily reused. Otherwise, the teams step just duplicates the schedule’s teams tab
We’re able to add more context about number of games produced in the helper text of certain inputs. Originally this wasn’t entirely certain as the teams step came after
Cross group schedules
Selecting two groups will produce a cross-group schedule
Previously you would select no group then select the team/group in the teams step. This no longer exists, so you need to specify the groups that will be crossed
Two possible implementations:
groupId
/groupIds
orgroupId
/crossGroupId
. This is just as an API since options are no longer persistedIdeally it's possible to select two groupIds within the same group input, but it could be better UX to just introduce a cross-group switch that shows another group input to help enforce the notion you’re only crossing two groups
Game numbers are pulled from the sequence of the home team group
Resulting games do not have a group associated to them, existing logic around stats does not change
...
Uploaded
This can behave exactly like existing import modals
Will still need to reuse logic of matching teams and arenas
...
Manual
This just becomes creating a single draft game at at time, so there’s no special flow necessary as the only configuration was a starting game number
Need to make sure current behaviour of autoincrementing a starting number is maintained in any case
Updates
When a DraftGame is created, search for an existing game the schedule by number and link the gameId automatically. Not applicable on updates.
This will become relevant later when reusing this functionality for game change requests
When editing and display the draft game, clearly show that a game will be updated as a result of publishing
...
We must maintain the existing analysis functionality and move this into an API
The great thing is it’ll be very easy now to mix the published games and draft games and show the analysis at all times in the schedule view (and potentially even the office)
Would want to allow being able to toggle showing draft games so you can see what your schedule is like currently and how the draft games will affect it
🚩 Rounds
Models
Draft
Deprecated. Unpublished games will be created as DraftGame in the migration
...