[Feature] Return content as array instead of json encodable string

[sidz]

Hi.

First of all I'd like to say thank you for this library it is really helpful.

It would be nice to improve getContent method and return request/response as an array instead of string. As currently getContent returns json encodable string. For example:

{
  "message": "Response content: \"200 https://fake.api.com\"",
  "context": {
    "request": "{\"property\":\"99544\"}",
    "response": "{\"id\":\"13793060365814579204730000\"}",
    "info": {}
  },
  "level": 200,
  "level_name": "INFO",
  "channel": "http",
  "datetime": "2025-05-16T10:03:31.444186+00:00",
  "extra": {}
}

As developer I'd like to see array as it's better from readability point of view. Like:

{
  "message": "Response content: \"200 https://fake.api.com\"",
  "context": {
    "request": [
        "property" => "99544",
        ... additional properties
    ]",
    "response": [
        "id" => "13793060365814579204730000",
        ... additional properies
    ],
    "info": {}
  },
  "level": 200,
  "level_name": "INFO",
  "channel": "http",
  "datetime": "2025-05-16T10:03:31.444186+00:00",
  "extra": {}
}

p.s. so it would be identical what guzzle middleware does. For reference: https://github.com/gmponos/guzzle-log-middleware/blob/master/src/Handler/MultiRecordArrayHandler.php#L143-L148

[liborm85]

Implemented by commit 775b046.

Added toArray() method to convert JSON request/response data into an array for use in the logger's request, response contexts and request_body in info.

[sidz]

Thanks for the quick solution but it would be really good if getContent returns array or string depending on the Content-Type header our of the box so developers won't need to add their own Loggers.

I could invest some time to improve it if you think it's okay

[liborm85]

I based this on the implementation in Symfony HTTP client, where the getContent() method is used to retrieve a string, and toArray() is used to retrieve an array.
The getContent() method returns the raw request/response data as a string, so it's not appropriate for it to sometimes return a string and other times an array - such hybrid behavior could be confusing and problematic for developers.

The current approach is universal:

• If a developer wants a string, they call getContent()
• If they need an array, they use toArray()
• For automatic handling, the developer can use something like:
  $outputForLog = $context['response']->toArray() ?? $context['response']->getContent()
  However, this is problematic for further processing, as the return type depends on what the URL returns - either a string or an array - which can lead to inconsistencies in handling the response.

This approach offers a universal solution, allowing developers to clearly define what type of data they expect to work with.

[liborm85]

Feature released in version 1.2.0 and 2.2.0.