Align function signatures about cloudflare-go HOT 4 CLOSED

Q: What benefit does passing Zone as the function argument give (today, and in the future) if we require the user to do the name => ID lookup prior?

I 100% agree that rationalizing the function signatures is useful, and would be OK with a functions accepting a zoneID string instead of a zoneName string.

We can provide a helper function around the API—ZoneByName(zoneName string) (string, error) via GET /zone?name=$name—that returns the zoneID for the package user to cache locally and then pass to functions as needed. The package user can async that as needed (via a waitgroup or channels) if they have a bunch of zones to lookup.

from cloudflare-go.

Initially I wanted as little friction as possible for users of the library/API so thought it made more sense, in most cases, to pass in the zone name and have the function do the zone ID lookup for you. There were one or two cases where it seemed to make more sense to use the object instead.

I do agree that this needs cleaning up and made more consistent.

from cloudflare-go.

Accepting Zone instead of a zone ID would mean we could check if the plan of a zone allow an action to be made, without firing a request to the API. That's the only thing I could think of from the top of my head, and may not be enough reason to require users to use Zone everywhere.
I think accepting the zone ID as a string would be the best option then.

from cloudflare-go.

This was done in #22.

from cloudflare-go.