Why?

Most request configuration should happen at the client level, not the global level. The global value is still used as an initial default, but it'll be removed in the future.

note: I couldn't get end-to-end tests for this working because of problems with getting the mocks right. I've done some local testing and feel good about it working, but I'd feel better with a unit test. We can follow up with that or pair on it, if you'd like.

What?

• add max_nextwork_retries to RequestOptions, making it available to every method
• parse those options out of $config during RequestOptions parsing
• add arguments to pass that value down through all of the request-related methods
• add tests

See Also

• DEVSDK-1446

Changelog

• Allow setting maxNetworkRetries at the StripeClient level via a new argument to the RequestOptions constructor
  • ⚠️ (potentially breaking) a client's configuration for maxNetworkRetries is set during client initialization. Subsequent calls to Stripe::setMaxNetworkRetries() after client creation won't affect that client.
• Allow setting maxNetworkRetries per-request via the max_network_retries config argument. This works for both the service and resource based patterns. In both cases, an explicitly passed value takes precedence over the global (or client) value.