...
The current schedule info step is split into multiple steps for matchups and scheduling in the modal
Starting game number input would no longer be necessary as we would use game numbering sequences instead
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
🚩 How does cross-group scheduling work?
Game numbers should be pulled from the home team’s sequence
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/groupIdsorgroupId/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
...