Creating an Assert:datetime method

[JasonBenett]

The goal is to create a fast way to assert that a string match a given date pattern. Something like:

Assert::datetime($myStringDate, 'Y-m-d H:i:s', 'My message');

What do you think about it ?

[zerkms]

What is the suggested workflow?

Assert::datetime($myStringDate, 'Y-m-d H:i:s', 'My message');

$dt = \DateTime::createFromFormat('Y-m-d H:i:s', $myStringDate);
Assert::notNull($dt);

If something like ^ then the first assert looks redundant. Or you have something else in mind?

[JasonBenett]

As a pure assertion, for me, the goal is not to create the datetime object but just controlling that the given string is a well formatted datetime. If, for instance, I extends this library to build assertions via PHP annotations, my goal will not be to create instances but just checking things such as Symfony Constraints do it for example.

It's useful when you receive some data from an API or when you are working with DTO for instance.

[JasonBenett]

@zerkms What do you think about this idea? I saw there is a PR in that way too. We are currently asserting emails and uuids. Why should it be different for a date or a datetime given as a string?
I can create the PR without any problem :-)

[zerkms]

I'm just another contributor not a core developer here :-)

If I led the project I wouldn't let emails and uuids as well, as I think those encapsulate too much of domain-specific knowledge.

[jokaorgua]

I would like to use such an assertion too.

[King2500]

What is the suggested workflow?

Assert::datetime($myStringDate, 'Y-m-d H:i:s', 'My message');

$dt = \DateTime::createFromFormat('Y-m-d H:i:s', $myStringDate);
Assert::notNull($dt);

If something like ^ then the first assert looks redundant. Or you have something else in mind?

I would rather call the above kind of check dateTimeFormat.

Under dateTime I would suggest this check:

try
{
    new \DateTime($dateTimeString);
    return true;
}
catch (\Exception $ex)
{
    return false;
}