Page Comparison

...

Once the information from the draft modal is filled out, draft games are created and they’ll be available in cards on the schedule, office and office pages. teams pages.

Having a new card being available on these different pages allows schedulers flexibility on how they want to schedule. They could go to the office page for the league to schedule all divisions at once, or to an association page to focus on games involving that association. The card will also have additional filters available to be able to fine-tune to the desired context.

The card will work identical to how the games step currently works with the calendar drag and drop mode being available. We can make use of card expanding (from the reports card) to provide more space to schedule games and use the calendar, or provide a dedicated tab instead.

...

• The current schedule info step is split into multiple steps for matchups and scheduling in the modal

• Starting game number input is no longer necessary as drafts 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

• When specifying game per team, limit the total games to even numbers to prevent unbalanced schedules

• 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 or groupId/crossGroupId. This is just as an API since options are no longer persisted

    • Ideally 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

...