Deprecate not passing the--show-arguments option when a service name is provided. The next step will be to deprecate--show-arguments in8.0.

So with Symfony 7.3 and 7.4, I would see a deprecation if I don’t use--show-arguments, that would encourage me to use this option.

Then in Symfony 8.0, using the--show-arguments option would show a deprecation message?

That sounds counter-intuitive.

Or we could add--hide-arguments now in 7.3 and deprecate not setting one or the other. But do we really want to have thathide-arguments ultimately? Not sure we need it.

Asking to opt-in the behavior we want to be the only possible one, before making it the default one and removing the capacity to opt-in/out is what we usually do I think.
So apart from the fact that the option should be deprecated in 8.1 instead of 8.0, which makes a difference, the proposed plan looks good to me.

I would keep things simple here:

• Always show arguments
• Deprecate--show-arguments and make it a noop in 7.3
• Remove--show-arguments in 8.0

Indeed, command output is not covered by our BC promise. If someone parses the output, they should opt for--format=json.

Thejson output will be impacted by this change but that’s fine for me 🙌

Thejson output will be impacted by this change but that’s fine for me 🙌

Not really, the only difference is that we'll always have the arguments.

Yes that’s what I mean, the output will now have anarguments key by default so a 1:1 assertion won’t pass anymore.

I updated the code to always show arguments.
Some unit tests are failing but I believe it's not because of my changes.

Please also add a note in the framework-bundle's CHANGELOG and UPGRADE-7.3 about the deprecation.

@Florian-Merle, thank you!

Good luck with this PR, looking forward to better DX withdebug:container in 7.3!

The PR title doesn't match anymore with what the PR does.

Thank you@Florian-Merle.