You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We are working with a service that is mostly JSON but that has some resources that return binary data (images). Trying to accommodate this with the current version of Guzzle Services is inconvenient because the option as to whether or not a response should be parsed/processed is specified in the service client config instead of in the operation config.
My current workaround is that all of our requests go through a services tier/request facade. That facade uses one version of the Guzzle services client for requests that need JSON, and a different version for binary requests. But that also means we have to remember not to invoke the wrong service commands on the wrong client, OR we have to keep the configurations for the two types of clients separate.
Instead, it would be great if I could provide a config like this:
operations:
getFile:
httpMethod: 'GET'process: falseuri: 'serve/{file_id}'parameters:
file_id:
location: 'uri'description: 'The unique identifier of the file being requested.'type: 'integer'required: trueminimum: 1
The key is process: false. This is not currently supported.
The text was updated successfully, but these errors were encountered:
We are working with a service that is mostly JSON but that has some resources that return binary data (images). Trying to accommodate this with the current version of Guzzle Services is inconvenient because the option as to whether or not a response should be parsed/processed is specified in the service client config instead of in the operation config.
My current workaround is that all of our requests go through a services tier/request facade. That facade uses one version of the Guzzle services client for requests that need JSON, and a different version for binary requests. But that also means we have to remember not to invoke the wrong service commands on the wrong client, OR we have to keep the configurations for the two types of clients separate.
Instead, it would be great if I could provide a config like this:
The key is
process: false
. This is not currently supported.The text was updated successfully, but these errors were encountered: