...
Instead, we’ll move away from the single Draft model to a parallel games table (likely called DraftGames) which we can work with like any other model.
Table of Contents |
---|
Requirements
Draft games need to be shared to associations who need to be able to view all their draft games in one place regardless of schedule
Draft games must be in their own model to make this relation feasible
Draft games may impact availability as soon as they’re scheduled even if not yet “published”
This setting currently exists
If a draft game is rescheduling an existing game this should be clearer
Currently this matches on game number
More flexibility on draft creation flows
Currently it’s a rigid info/teams/review/publish flow, certain options may require more details for improved UX
Should be possible to partially publish some draft games when they’re ready
e.g., one association is done early but others aren’t ready yet
...
This can live behind a feature flag under development, as the isolation of drafts makes this convenient.
...
Model changes
Status | ||
---|---|---|
|
Add order to ScheduleTeam
Create DraftGame, add a new card to show them in place of Drafts per flag
Implement game number sequence
Manual creation
Status | ||
---|---|---|
|
Modal to create draft games one by one via the new DraftGame card
Select multiple games to publish, share, or delete
Analysis dialog
Status | ||
---|---|---|
|
Move the game analysis logic into a library and accessible through the API
Provide an analysis dialog on the schedule page
Import modal
Status | ||
---|---|---|
|
Follow the existing importers to parse a file
This would import as draft games as well as schedule teams
Should we provide an option to publish directly?
Generation
Status | ||
---|---|---|
|
Create a stepper modal that mimics the existing cards
New
POST /schedules/:id/generate
API would accept the parameters and create draft games
Release
Status | ||
---|---|---|
|
Existing unpublished drafts to be converted to draft games
Remove flags, UI and deprecate API