I am not sure that we really want to do that as it calls for conflicts when merging7.4 into8.1.

Thanks for proposing this "modernization" :)

However, I don't think we can do this given ourbackwards compatibility promise unfortunately. Given these classes aren't internal, we must make sure they remain ancestors of theCommand class as applications might rely on this (e.g. when passing the instance to a method expecting aCommand type). The same applies to theconfigure()/execute() commands, someone might have decorated or overridden these methods in a child class and we must make sure that doesn't break.

So I don't think we can do anything here, and all existing commands in Symfony must keep using theCommand public API instead of the invokable command one (unless someone comes up with a genius smooth upgrade path).

I agree with@wouterj. It's a BC break which we don't gain much from. I don't believe we should do this.

Thanks for proposing though.