See commits for details
See commits for details
el-shift-event-cleanup into main See commits for details
A bunch of methods still expected the type of eventable (ShiftEvent) as an argument. But ShiftEvent is unused so we can remove this argument.
Since we don't have two separate models, the separation of their attributes is not used and adds unneeded complexity. The EventsService and related classes now act on a single hash of attributes.
Now that all the EventsService objects take a single hash of params, we can merge them in the view and controller. I'd love to have better flow for adding tasks and users. The way it works now is we set `task_ids` (or `user_ids`) in an array with the field_name `event[task_ids][]`. If the `commit` param is `ADD TASK`, it adds a select tag with that name, adding another value to the form params. I also tried to use the `accepts_nested_attributes_for` pattern with `fields_for(:tasks)`. The problem I ran into there was that rails expects that the tasks _already_ belong to the event. When you're adding them before creation or updating, rails throws a get an `ActiveRecord::NotFound` error. Setting an array of `task_ids` seems to be the best option I can find for now.
No due date set.
No dependencies set.
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?