Conditional Validation: More then "when"

[tchari]

When is a great rule for a binary case. Is there a rule or way to do conditional validation if the conditional key value can have more than two outcomes?
e.g.

    $cars = [
      ['manufacturer' => 'Honda', 'model' => 'Accord'],
      ['manufacturer' => 'Toyota', 'model' => 'Rav4'],
      ['manufacturer' => 'Ford', 'model' => 'notarealcar']
    ];
    Validator::arrayType()->each(
      Validator::key('manufacturer', Validator::in(['Honda', 'Toyota', 'Ford']))
      ->when(
        Validator::key('manufacturer', Validator::equals('Honda')),
        Validator::key('model', Validator::in(['Accord', 'Fit'])),
        Validator::when(
          Validator::key('manufacturer', Validator::equals('Toyota')),
          Validator::key('model', Validator::in(['Rav4', 'Camry'])),
          Validator::key('model', Validator::in(['F150', 'Bronco']))
        )
      )
    )->assert($cars);

This code works, but chaining 'when' gets a little cumbersome after a few 'manufacturers'. Is there some kind of switch-like rule?

[alganet]

The oneOf and allOf are the perfect conditional validators for this. You can use:

$cars = [
    ['manufacturer' => 'Honda', 'model' => 'Accord'],
    ['manufacturer' => 'Toyota', 'model' => 'Rav4'],
    ['manufacturer' => 'Ford', 'model' => 'notarealcar'],
    ['manufacturer' => 'Honda', 'model' => 'not valid'],
];

try {
    Validator::arrayType()->each(
        Validator::oneOf(
            Validator::key('manufacturer', Validator::equals('Honda'))
                ->key('model', Validator::in(['Accord', 'Fit'])),
            Validator::key('manufacturer', Validator::equals('Toyota'))
                ->key('model', Validator::in(['Rav4', 'Camry'])),
            Validator::key('manufacturer', Validator::equals('Ford'))
                ->key('model', Validator::in(['F150', 'Bronco']))
        )
    )->assert($cars);
} catch (NestedValidationException $e) {
    var_dump($e->getMessages());
}

This behaves like an if...elseif block, or a set of OR conditions.

While testing this, I noticed that my recent changes to Each were broken for this example. It should, however, work for 2.2 (except for the reporting problems) and now it is fixed on 2.3 as well (with detailed messages).

[alganet]

I'm closing this because it was supported before. There is an improvement related to it, but it is about the message reporting in Each and not the structuring of the oneOf itself.