Updating operations to accept generic request options instead of just query parameters #522
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is an update to the
4.x
version of the client.Operations now require that query string parameters be specified under the
params
key of the$options
parameter. This will allow for additional options to be specified in requests. Currently, this only includes custom headers, but may be expanded in the future.This pull request also adds the
getRequest()
method to the\Recurly\Response
class for debugging purposes.In the
3.x
version of the client, query string parameters would be specified directly on the$options
parameter of the operation:With this update, the
params
key must be added to the$options
. Additionally, aheaders
key may be added: