Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Explicitly allow
associated_trip_id
for any event type
This implements the change suggested in #289 by clarifying that any trip-ending event can and should have an `associated_trip_id`, not just `user_drop_off` events. Since the Provider event system currently doesn't define which states are allowed to transition to which other states, it's already spec-compliant to follow a `reserved`/`user_pick_up` event with an `unavailable`/`low_battery` event, and this is the most semantically-accurate way to describe the scenario where a device shuts down during a trip because of low battery. In this situation, the implementer should include an `associated_trip_id` field in both events so that API consumers can correctly identify these events as the endpoints of the relevant trip.
- Loading branch information