Fixes #15
Picture a recurring event where future events have a volunteer but an earlier one does not. Adding that same volunteer to the earlier shift and all future shifts creates a "conflict" that we warn organizations about. That email is sent to the organization's internal_alerts_email.
If they don't have an email in that field, we would crash!! Instead of that, we put a message reminding them to fill out that email, and continue on successfully.
please add alert
Technically this works by returning a result object from the mutating EventsService methods (except delete ones). Before this, if a problem happens inside the EventService, we didn't have a great
way of dealing with it outside that service. update, update_into_future, and post_occurrence_details all now return an EventResult which contains an event and flash messages (sometimes empty). The controller can then still access the event, but also let the user know about other problems (or celebrations).
I didn't add them to the delete methods because nothing actually expected any events to be returned from them.
I also enabled mailer errors in development because they were off and it took me a while to figure out how to reproduce the bug.
Fixes #15
Picture a recurring event where future events have a volunteer but an earlier one does not. Adding that same volunteer to the earlier shift and all future shifts creates a "conflict" that we warn organizations about. That email is sent to the organization's `internal_alerts_email`.
If they don't have an email in that field, we would crash!! Instead of that, we put a message reminding them to fill out that email, and continue on successfully.

Technically this works by returning a result object from the mutating `EventsService` methods (except delete ones). Before this, if a problem happens inside the `EventService`, we didn't have a great
way of dealing with it outside that service. `update`, `update_into_future`, and `post_occurrence_details` all now return an `EventResult` which contains an event and flash messages (sometimes empty). The controller can then still access the `event`, but also let the user know about other problems (or celebrations).
I didn't add them to the delete methods because nothing actually expected any events to be returned from them.
I also enabled mailer errors in development because they were off and it took me a while to figure out how to reproduce the bug.