Closed alex-bellon closed 2 years ago
Definitely annoying that we missed that naming inconsistency. Is this request for a fix just for consistency reasons or do you have a specific library/use in mind that relies on the name being the same? If the former I'd rather not add more logic
The request was for consistency, I had just come across the discrepancy when writing a script that was using the API and was getting errors when I tried using lng
. I understand not wanting to add more logic though so feel free to close the issue.
In the response for
api.helium.io/v1/hotspots/location/distance
,api.helium.io/v1/hotspots/:address
, etc. the longitude variable is namedlng
, but in the request forapi.helium.io/v1/hotspots/location/distance
it uses the variable namelon
.Maybe the request for
api.helium.io/v1/hotspots/location/distance
could also supportlng
as not to break anything.