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
As stated in the title running the library with php 8.1 trigger an unexpected behavior with \GuzzleHttp\Psr7\Stream::getContents.
For instance in ContactApi::requestContactExportWithHttpInfo this code:
if ($returnType === '\SplFileObject') {
$content = $responseBody; //stream goes to serializer
} else {
**$content = $responseBody->getContents();**
if ($returnType !== 'string') {
$content = json_decode($content);
}
}
return a $content = "".
I didn't go into details, but I found that might be a stream issue.
If I cast $responseBody into a string it works as expected since $content turn to be something like {"processId":90} thank to magic method GuzzleHttp\Psr7\Stream::__toString.
$content = (string) $responseBody;
Maybe it's a guzzle http issue, not a brevo php sdk issue.
Thanks in advance
The text was updated successfully, but these errors were encountered:
I found that the problem is connected with the logging operation. Since it consumes the stream messagge it is not available for reading it again, unless the client api force the rewind of the stream, which is accomplished for instance with the magic method __toString ($content = (string) $responseBody;) as stated above.
I guess it could be improved in swagger-codegen code generation.
As stated in the title running the library with php 8.1 trigger an unexpected behavior with
\GuzzleHttp\Psr7\Stream::getContents
.For instance in
ContactApi::requestContactExportWithHttpInfo
this code:return a
$content = ""
.I didn't go into details, but I found that might be a stream issue.
If I cast $responseBody into a string it works as expected since $content turn to be something like
{"processId":90}
thank to magic methodGuzzleHttp\Psr7\Stream::__toString
.Maybe it's a guzzle http issue, not a brevo php sdk issue.
Thanks in advance
The text was updated successfully, but these errors were encountered: