{"push_id":657102239,"size":1,"distinct_size":1,"ref":"refs/heads/master","head":"d2a35b36ab4b452712cb932a9b74951849de786d","before":"9bae8db8f47bf6b249cdbfc0bbe76e181220e133","commits":[{"sha":"d2a35b36ab4b452712cb932a9b74951849de786d","author":{"email":"f75897670c17327c42ab201733fb8a81ff9f4c34@tremily.us","name":"W. Trevor King"},"message":"public.json: Add 'GET /route-stops' and /route-stop/{id} endpoints\n\nWe only create stops at verification time, but folks will want to have\nestimated delivery times while they're shopping for their order.\nDavid confirmed that a single model should store the usual offset\nbetween the start of delivery and a given drop on a route, so we need\nto expose that data publically.  This commit specifies that API and\nadjusts the stop description to explain that it's only useful for\nverified trips.\n\nThe duration format specifies ISO 8601 durations [1,2].  I've proposed\nit for inclusion in future versions of Swagger [3], but until that's\naccepted we're using it as a custom format [4].\n\n[1]: https://tools.ietf.org/html/rfc3339#page-13\n[2]: http://en.wikipedia.org/wiki/ISO_8601#Durations\n[3]: https://github.com/swagger-api/swagger-spec/issues/359\n[4]: https://github.com/swagger-api/swagger-spec/blob/master/versions/2.0.md#data-types\n     Swagger uses several known formats to more finely define the data\n     type being used. However, the format property is an open\n     string-valued property, and can have any value to support\n     documentation needs. Formats such as \"email\", \"uuid\", etc., can\n     be used even though they are not defined by this specification.","distinct":true,"url":"https://api.github.com/repos/azurestandard/api-spec/commits/d2a35b36ab4b452712cb932a9b74951849de786d"}]}