{"push_id":1237718585,"size":1,"distinct_size":1,"ref":"refs/heads/location-lists","head":"437028dbdc9cc93368d7e261adbf7a71ec84ce27","before":"262de37ccf001d4023f6e3ec1458d9b880a1707e","commits":[{"sha":"437028dbdc9cc93368d7e261adbf7a71ec84ce27","author":{"name":"Marc Ryan","email":"3836b9f8973a30326b24282b2f86954a1a348051@gmail.com"},"message":"fix(locationLists): fix methods for retrieving/updating unresolved locations\n\nSwagger documentation for the following two endpoints was incorrect:\n  1) PUT /v1/location_lists/{location_list_id}/upload/{file_upload_id}/unresolved_locations\n  2) PUT /v1/location_lists/{location_list_id}/upload/{file_upload_id}/unresolved_locations/{location_id}\n\n1) Although this endpoint does support PUT, there was no documentation describing the body of the request.\nAfter reviewing the Gigwalk API, I believe this should be describing the GET operation. This makes sense\nas there is currently no swagger documentation for that method.\n\n2) Technically, there is nothing wrong with the documentation for this method, but it's a bit misleading.\nThe location_id parameter is not used anywhere in the API source code, so it should be removed altogether.\nI updated our client to not even expose this parameter.","distinct":true,"url":"https://api.github.com/repos/gigwalk-corp/gigwalk-node/commits/437028dbdc9cc93368d7e261adbf7a71ec84ce27"}]}
{"actor":{"display_login":"inv8der"}}