Add a long list of missing params and properties

[remi-stripe]

r? @brandur-stripe
cc @mickjermsurawong-stripe who found all of those for us.
cc @stripe/api-libraries

[remi-stripe]

This is a breaking change and likely requires a major version to play it safe even if it likely did not work.

[brandur-stripe]

All changes look good to me Remi!

And wow — it's so cool that we caught all these before a user noticed and complained about any of them! WE (finally) HAVE THE TECHNOLOGY.

[mickjermsurawong-stripe]

One more created range here please @remi-stripe
https://stripe.com/docs/api/refunds/list#list_refunds-created

[mickjermsurawong-stripe]

@brandur-stripe, would like your thoughts on representing empty string as a way to unset params please? These are a pattern of params we currently don't support in Go but it's in OpenAPI.
This corresponds to our backend param with :allow_present_but_empty but it can have different semantic based on endpoint. For example, billing_thresholds
https://stripe.com/docs/api/subscriptions/update#update_subscription-billing_thresholds

Pass an empty string to remove previously-defined thresholds.

On a separate note, I would like to keep this PR opened for at least this week, in case I missed flagging params among things we decided to actually not support and the empty string param.

[remi-stripe]

@mickjermsurawong-stripe IMO we should not keep such a PR open for a week. There's no real upside to "waiting until we find more", we would just do a brand new PR at that point.

I also think the empty params should be resolved entirely separately and not in this PR. We should also talk about the best approach internally instead.

[mickjermsurawong-stripe]

ah that's fair. I'm good with merging this then
LGTM

[brandur-stripe]

I also think the empty params should be resolved entirely separately and not in this PR. We should also talk about the best approach internally instead.

+1. I think we're going to need to add a new property (e.g. Empty) and custom encode function to support this properly unfortunately.

[mickjermsurawong-stripe]

The build was stuck but seems working now. I can take the release

[remi-stripe]

@brandur-stripe yeah I canceled and restarted. Leaving the release to you, thanks a lot! Reminder that it's a major version to be safe

[brandur-stripe]

Released as 60.0.0.

[mickjermsurawong-stripe]

ah thank you @brandur-stripe! i'm just about reading instructions and preparing the release message!

[brandur-stripe]

ah thank you @brandur-stripe! i'm just about reading instructions and preparing the release message!

Oops, sorry @mickjermsurawong-stripe — I didn't mean to step on your toes. Somehow I read the "you" in as meaning me, hah (which reading through again makes no sense I see).