This PR introduces support for using DTOs as command inputs in Console commands through a new #[Input] attribute. Especially useful for commands with many arguments and options, as it prevents cluttering the __invoke() method with lengthy parameter lists and their associated attributes and options.

Example:

class UserDto
{
    #[Argument]
    public string $email {
        set => strtolower($value);
    }

    #[Argument]
    public string $password;

    #[Option]
    public bool $admin = false;
}

The command's arguments and options are defined directly on the DTO's properties. These properties need to be public, and now you can use property hooks to normalize the value when necessary.

#[AsCommand('app:user:create')]
class CreateUserCommand
{
    public function __invoke(#[Input] UserDto $user): int
    {
        // Create new user with $user->email, $user->password, etc.

        return 0;
    }
}

$ bin/console help app:create-user
Usage:
  app:create-user [options] [--] <email> <password>

Arguments:
  email
  password

Options:
      --admin|--no-admin

✨ Input validation and handling become naturally simpler 😉

It also supports splitting the command input across multiple DTOs (e.g. grouping inputs into UserDto and GroupDto), or more complex structured like nested DTOs:

class UserDto
{
    #[Argument]
    public string $email;

    #[Argument]
    public string $password;

    #[Option]
    public bool $active = true;

    #[Input]
    public ProfileDto $profile;
}

class ProfileDto
{
    #[Argument]
    public string $name;

    #[Option]
    public ?string $phone = null;
}

Thus, we can model the command input while defining its arguments and options. Here's the resulting usage output from the previous definition:

Usage:
  app:create-user [options] [--] <email> <password> <name>

Arguments:
  email                     
  password                  
  name                      

Options:
      --active|--no-active  
      --phone=PHONE

Food for Future PRs

• Automatic validation (if Validator component is installed) with proper error output from the violation list.
• Defers input interactivity (i.e. the Command::interact() method) to the DTO class.

Cheers!