feat(commands): take a backed enum as a command option

[mikield]

A fixed set of values had to be written as a string option with a choice list beside it:

#[Option(description: 'Where you play.', choices: ['PC' => 'PC', 'PlayStation' => 'PS4', 'Xbox' => 'X1'])]
string $platform,

Two places to change and one to forget, and the handler still receives a bare string it has to validate itself.

#[Option(description: 'Where you play.')]
Platform $platform,

The framework already resolved backed enums for a component's arguments (ComponentArgumentResolver); a command's options were the one place it did not. Now:

• a string-backed enum becomes a STRING option, an int-backed one an INTEGER option;
• every case is offered as a choice, unless choices: says otherwise;
• the handler is given the case, not the value.

Naming the cases

A case name is a PHP identifier, in English, and rarely what a bot wants shown — PlayStation happens to read well, NorthAmerica does not. An enum may implement Choosable to say how each one reads:

enum Platform: string implements Choosable
{
    case PlayStation = 'PS4';

    public function label(): string { /* ... */ }
}

Without it the case name is used, which is at least a name somebody chose.

A value that is not a case

Discord checks a choice against the list it was given, so this can only come from a client that made one up. It names the option and the value rather than surfacing a ValueError from deep inside from().

Also sets scanDirectories for tests/Fixtures — they are excluded from analysis, but a test naming one still has to resolve to something.

🤖 Generated with Claude Code

[github-actions]

🎉 This PR is included in version 0.12.0 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀