[question]: Making signing logic exported about google-maps-services-go HOT 5 CLOSED

Cool, thanks for the clarification. I'm glad the current design is workable for you.

from google-maps-services-go.

I'd kinda prefer not to expose the signing logic. Is it possible to feed your requests through the static map API?

from google-maps-services-go.

I understand, but for some reasons, it doesn't fit for us.
It would work if StaticMapRequest had method SignURL(clientID string, secret []byte)

for instance:

// create request
r := StaticMapRequest{}
s := r.SignURL(clientID, secret) // staticMapAPI.path is used inside

Unfortunately, AFAIU in that case, it should be added to each request for consistency, and this is not a good way.

Anyway, thanks for helping!

from google-maps-services-go.

Can you explain how the addition of this method to the StaticMapRequest would help?

from google-maps-services-go.

Sure. I have a mobile client that has already had an implemented logic showing pictures generated via StaticMap API. It used to work with API_KEY until the rules have changed.

Now it sends to the backend a StaticMap API query for signing. As for instance, a query client=clientID&origin=Toronto gets a signed URL https://maps.googleapis.com/maps/api/staticmap?client=clientID&origin=Toronto&signature=mPvi3crsSSM1olW2lXmzUWcLB_8= as a response.

I agree that my previous proposal is not correct. Having a method Sign is useless, cause it adds extra step of converting client=clientID&origin=Toronto -> StaticMapRequest.

In case, of making Sign func public, private apiConfig should be exported as well.

So, I think the current implementation is good enough.

from google-maps-services-go.