Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add new battery_charged event type reason #237

Merged
merged 1 commit into from
Feb 26, 2019
Merged

Add new battery_charged event type reason #237

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions agency/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -191,6 +191,7 @@ List of valid vehicle events and the resulting vehicle status if the event is su
| `event_type` | description | valid initial `status` | `status` on success | status_description |
| ---------------------- | ---------------------------------------------------------------------------------------------------- | -------------------------------------------------- | ------------------- | ----------------------------------------------------------------------- |
| `service_start` | Vehicle introduced into service at the beginning of the day (if program does not operate 24/7) | `unavailable`, `removed`, `elsewhere` | `available` | Vehicle is on the street and available for customer use. |
| `battery_charged` | A vehicle becomes available because its battery is charged enough | `unavailable` | `available` | |
| `trip_end` | Customer ends trip and reservation | `trip` | `available` | |
| `rebalance_drop_off` | Vehicle moved for rebalancing | `removed` | `available` | |
| `maintenance_drop_off` | Vehicle introduced into service after being removed for maintenance | `removed` | `available` | |
Expand Down
1 change: 1 addition & 0 deletions generate_schema/provider/status_changes.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -120,6 +120,7 @@
},
"event_type_reason": {
"enum": [
"battery_charged",
"service_start",
"user_drop_off",
"rebalance_drop_off",
Expand Down
1 change: 1 addition & 0 deletions provider/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -275,6 +275,7 @@ When multiple query parameters are specified, they should all apply to the retur
| `event_type` | Description | `event_type_reason` | Description |
| ---------- | ---------------------- | ------- | ------------------ |
| `available` | A device becomes available for customer use | `service_start` | Device introduced into service at the beginning of the day (if program does not operate 24/7) |
| | | `battery_charged` | A device becomes available because its battery is charged enough |
| | | `user_drop_off` | User ends reservation |
| | | `rebalance_drop_off` | Device moved for rebalancing |
| | | `maintenance_drop_off` | Device introduced into service after being removed for maintenance |
Expand Down
3 changes: 2 additions & 1 deletion provider/status_changes.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -311,6 +311,7 @@
},
"event_type_reason": {
"enum": [
"battery_charged",
"service_start",
"user_drop_off",
"rebalance_drop_off",
Expand Down Expand Up @@ -400,4 +401,4 @@
}
},
"additionalProperties": false
}
}