Error in DateValidator with php format "c"

[SOHELAHMED7]

I observed a strange behaviour of \yii\validators\DateValidator.

From PHP docs

c	ISO 8601 date	2004-02-12T15:19:21+00:00

What steps will reproduce the problem?

$v = new DateValidator([
            'type' => 'datetime',
            'format' => 'php:c'
        ]);

        Case 1:
        $v->validate('2004-02-12T15:19:21+00:00', $err);  <---- this example is from php.net
        VarDumper::dump($err); <---  'The format of the input value is invalid.'

        Case 2:
        $v->validate('2004-02-12T15:19:21+0000', $err);
        VarDumper::dump($err); <---  'The format of the input value is invalid.'

---

$v2 = new DateValidator([
            'type' => 'datetime',
            'format' => 'php:'.DATE_ATOM
        ]);

        Case 3:
        $v2->validate('2004-02-12T15:19:21+0000', $err);
        VarDumper::dump($err); <--- null

        Case 4:
       $v2->validate('2004-02-12T15:19:21+00:00', $err);
       VarDumper::dump($err); <--- null

What is the expected result?

For case 1 -> Validation should pass

What do you get instead?

For case 1 -> Validation fails

Additional info

Q	A
Yii version	2.0.47
PHP version
Operating system

[bizley]

This is a PHP issue, I can see that both c and r are not working. I'm not sure if it should be reported though, PHP says for example that their DateTimeInterface::ISO8601 should not be used since it's not really ISO8601 and to use ISO8601_EXPANDED or ATOM instead. Maybe this is the case as well? c looks like a weird mix between ISO8601 and ISO8601_EXPANDED.

We could throw an InvalidConfigException on init when php:c or php:r is used as a format with the suggestion to use proper formats.

[My6UoT9]

https://stackoverflow.com/a/38324318

[SOHELAHMED7]

@bizley

Yes that seems to be confusing

We could throw an InvalidConfigException on init when php:c or php:r is used as a format with the suggestion to use proper formats.

I disagree. Throwing error and preventing further execution is not the best option in my humble opinion. I suggest to log a warning/notice with details of the issue and suggesting work-arounds