Closed jcoyne closed 9 years ago
Good job wading into my tangled scheduler code!
The usual workflow for the scheduling is to generate a schedule on somebody's local machine (which is much, much faster than heroku), review it, then export it from the laptop & import it on heroku.
For that reason, app:clear_schedule
has limited utility. I'd be inclined to keep it a manual operation, given how dangerous it is. If we do include it, I'd recommend including some kind of sanity check (e.g. “type SCHEDULE ARMAGEDDON to confirm”).
@pcantrell Good advice. I've added a sanity check.
Ha, awesome. I meant “SCHEDULE ARMAGEDDON” just as a placeholder, but I guess it does catch one’s attention!
@pcantrell I can recognize a golden idea when I see it.
Sessions that are entered before the scheduler are run are now immutable with regards to their timeslot. They will not get scheduled elsewhere. This enable you to add sessions that have to be in a certain place at a certain time. The scheduler pays no-attention to them, so you only want to place them into Timeslots where schedulable is false. For example you may place a "Presenters Luncheon, rm 123" during the "Lunch" timeslot.
Also added a rake task
app:clear_schedule
This enables the generated schedule to be cleared so an alternate schedule can be generated.