Events used to have an ends_at attribute. In my mind, this was a misstep in
the data model. ends_at and starts_at were two independent fields that relate
to each other in the users mind, but the database had no concept of that. This
caused situations where ends_at could end before starts_at which made no
sense.
This switches to a duration instead. Users will still set an end time and not be
aware of this change. But it does reduce complexity somewhat and my hope is that
this change will reduce potential bugs.
Events used to have an `ends_at` attribute. In my mind, this was a misstep in
the data model. `ends_at` and starts_at were two independent fields that relate
to each other in the users mind, but the database had no concept of that. This
caused situations where `ends_at` could end before starts_at which made no
sense.
This switches to a duration instead. Users will still set an end time and not be
aware of this change. But it does reduce complexity somewhat and my hope is that
this change will reduce potential bugs.