Mixed types on API v2 endpoint to create a droplet about godo

[macb]

Ya, the API is lenient enough that it will attempt to parse the string as an integer. We shouldn't rely on that and instead correctly marshal CreateDropletRequest.Image as an int/string as required.

[nesv]

Frankly, I think this is more of a "no-no" on the API side. If the API is lenient enough to support numbers as strings, for private images, why not just enforce the type on the API, to always be a string?

[macb]

I agree it would be best to make the API less lenient but I also think it may be a bit too late for that as other clients may not exhibit this same behavior and may correctly pass an int or a string.

Either way it would be best to change the client to correctly follow the documented behavior of:

number (if using an image ID), or String (if using a public image slug)

Then if the behavior changes, we can correct the client as well.