CamelCaseKeys does replace keys in arrays

[boesing]

Hey there,

I am kinda used to work with laminas-hydrator and JMS.
Both only apply naming strategies only for object properties, which allows responses such as:

{
  "foo": {"bar_foo": "baz", "qoo_bar": true}
}

Which are passed to an object like:

final class Response
{
    /** @param array<string,mixed> $foo */
    public function __construct(public readonly array $foo) {}
}

In both JMS and Laminas Hydrator, the keys of foo won't get modified.
Sadly, the keys in CamelCaseKeys are all modified and thus, some stuff is not properly working as I'd expect it.

I can work around this for now by changing the response to a list of objects containing name and value but I wonder if this is just a niche case or if this should be addressed.

WDYT?