Jérôme Tamarelle

> I made the changes and added a test but i'm not sure if this is the best approach to test this. Let me know if there's a better way...

This transformation looks like the slug. Except it doesn't translate special chars to ascii. What is the use-case for kebab transformation?

Great. We already have `camel` and `snake`, adding `kebab` seems reasonable. Do you want to make a PR?

I don't think we can reliably detect if the web server is running with the same user or group as the running process. So I don't find it useful to...

The syntax that don't work is the one that rely on __destruct. The last suggestion mentioned by @nicolas-grekas is `dump()->trace()->maxDepth(4)->dump($var)` which returns the `$var` as expected.

> I don't really like the extra argument to handle the BC layer because it means we're going to have to deprecate it in 7.1 + remove it in 8.0....

That's very clever. I'll try to implement this solution.

After reflection by testing the implementation, as a user of this functions I prefer adding a 3rd argument to `getInt` instead of wrapping the method call with try-catch in order...

I'm not sure to understand your proposition. Here is code samples from user/developer view. Currently (getInt('invalid'); // returns 0 ``` With deprecation (6.3) ```php $inputs->getInt('invalid'); // returns 0 // and...

Hum, something like this? ```php public function getInt(string $key, int $default = 0): int { try { return $this->filter(/* ... */); } catch (\UnexpectedValueException|BadRequestException $e) { trigger_deprecation('symfony/http-foundation', '6.3', '...'); trigger_error($e->getMessage());...