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.

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

Dev changes #2

Merged
merged 54 commits into from
Apr 2, 2019
Merged

Dev changes #2

merged 54 commits into from
Apr 2, 2019

Conversation

jfh01
Copy link
Owner

@jfh01 jfh01 commented Apr 2, 2019

No description provided.

jannasmith and others added 30 commits February 12, 2019 13:51
When the battery of a device is too low, the service yields the
`unavailable` event type with the `low_battery` reason. Then the
device may charge itself (for example because it has been plugged to a
charging dock by the last customer, or because the device has a solar
panel). Once the battery is charged enough, the service can yield an
`available` event type with the `battery_charged` reason.

[closes #210]
drop UUID4 requirement in favor of simply UUID
…ll be developed in different endpoint(s) or API(s)
also clean up some telemetry wording
Depending on the actual device on board of the vehicle,
some information can be unavailable.
Add new `battery_charged` event type reason
…battery_charged

Revert "Add new `battery_charged` event type reason"
noting this missing step in ReleaseGuidelines
Fix broken link to Feb 7 webinar presentation
specify behavior for GET /vehicles with no device_id
Fixing a number of inconsistencies in the state diagram and adding a graphical representation.  Also, adding event_reason to separate the more granual event designators.
Mark Maxham and others added 24 commits March 1, 2019 11:54
…ced due to desire to handle out-of-order events
Consistency with Provider API
Remove reference to 412 for policy/business-logic
Updated to reflect that the process applies only to provider for now.
Clarified language around release notes and change descriptions.
Updated based on compliance changed approved by LADOT

Compliance will exist in a seperate document.
Approved by LADOT.   Updated compliance for in-trip telemetry for scooters.
@jfh01 jfh01 marked this pull request as ready for review April 2, 2019 19:42
@jfh01 jfh01 merged commit 3bcfaf1 into jfh01:master Apr 2, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

10 participants