Does Symfony DateTime validator support Y-m-dTH:i:s? - symfony

I need to validate dates in Symfony and the expected format is Y-m-dTH:i:s, for example 2019-08-02T23:09:01
This is how the DateTime object is being instantiated:
//...some code
'start_date' => new DateTime([
'format' => 'Y-m-dTH:i:s'
]),
//...some code
and even though start_date is correct (for example 2019-08-01T20:04:00), the validator still renders this invalid. If I try with 2019-08-01 20:04:00 and a format of 'Y-m-d H:i:s', then it works. Is it possible to use that T in the format?

Whats the origin of the date that you want to validate ? It's from form(user input?) ?
If yes
then you should use DateTime Assert on entity connected to form
https://symfony.com/doc/current/reference/constraints/DateTime.html
also
you can use datetime field (https://symfony.com/doc/current/reference/forms/types/datetime.html) on form to validate on data input
If no
If you have value from (for example) database, and you are not sure if is it vaild
you can use Datetime Assert ( link above) with validating "raw values" , here is example :
https://symfony.com/doc/current/validation/raw_values.html

Related

Symfony HiddenType for a DateTime object

I have a simple form
->add('createDateTime', HiddenType::class)
Causing an error:
Object of class DateTime could not be converted to string
How do I work around this issue? I don't want to change the entity to return a string formatted date...
Any ideas?
As form inputs require a text representation of the data, you'll need to convert the value to a string with the help of a DataTransformer. Fortunately, Symfony comes with a transformer for DateTime objects, you just need to add it to your form field:
$builder
->add('field') //...
->add('createDateTime', HiddenType::class);
$builder
->get('createDateTime')
->addModelTransformer(new DateTimeToStringTransformer());
You can specify different timezones for conversion or format if you need to.

Symfony 5 Convert string to datetime

In Symfony 5 I have a form where users enter into text fields and also a date. This is then redirected into a display controller that displays matching rows from the database. The date needed to be converted into a string for the redirect to work.
$firstName = $findPt->getFirstName();
$surname = $findPt->getSurname();
$username = $findPt->getUsername();
$dob = $findPt->getDateOfBirth();
$dobStringValue = $dob->format('Y-m-d');
return $this->redirectToRoute('app_displayClients', ['firstName' => $firstName,
'surname' => $surname,
'username' => $username,
'dob' => $dobStringValue]);
However in the display controller I then need to convert it back into a datetime to use it but that doesn't seem possible. I've tried various options, such as $dobDateTime= new DateTime($dateStr);
Please let me know if this question isn't clear or you need more information.
Many thanks in advance for any help.
You can reconvert it using DateTime::createFromFormat
$dobStringValue = $dob->format('Y-m-d');
$dobReconverted = \DateTime::createFromFormat('Y-m-d', $dobStringValue);
Thanks Agnohendrix, that was helpful. I didn't need to format as it was already a string but used $dobReconverted = \DateTime::createFromFormat('Y-m-d', $dobStringValue);
The \ seemed to have been what made it work, maybe this is something to do with using Symfony.
It works with "\Datetime" and not with "Datetime" because "Datetime" needs to be defined with a "use Datetime" to work; that's why the error "Did you forget a use statement for..." came out.

CakePHP date parsing in patchEntity [duplicate]

I try to save data from a cakephp 3 form. All data are well saved but datetime not. I've got 2 datetime fields. Those fields are filled by jquery-ui widget.
The problem seems to happened when pacthing entity.
$intervention = $this->Interventions->patchEntity($intervention, $this->request->data);
Debug of $this->request->data :
'user_id' => '1',
'description' => 'test',
'starttime' => '2015/11/15 10:00',
'endtime' => '2015/11/15 12:10'
Debug of my object $intervention after pacthEntity :
object(App\Model\Entity\Intervention)
'id' => (int) 3,
'user_id' => (int) 1,
'description' => 'test',
'starttime' => null,
'endtime' => null
...
starttime and endtime become null and I don't understand why.
Is somebody had this pb before ?
I tried (for debuging and understanding) to force fields value afer patching
and datetime fields in mysql are ok.
$intervention->starttime = date('Y-m-d H:i:s', strtotime($this->request->data['starttime']));
$intervention->endtime = date('Y-m-d H:i:s', strtotime($this->request->data['endtime']));
Thanks for help
Date/time values are being casted/parsed in a locale aware fashion
Update: this is the default behavior with the CakePHP application template versions prior to 3.2.5. As of 3.2.5 locale parsing is not enabled by default anymore, which will make the date/time marshalling logic expect a default format of Y-m-d H:i:s instead.
In the marshalling process, values are being "casted" according to the respective column types. For DATETIME columns, this is done by the \Cake\Database\Type\DateTimeType type class.
To be exact, this is done in \Cake\Database\Type\DateTimeType::marshall().
With the default app template configuration, DateTimeType is configured to use locale aware parsing, and since no default locale format is being set, \Cake\I18n\Time::parseDateTime() will parse the values according to its default "to string format" (Time::$_toStringFormat), which defaults to the locale aware [IntlDateFormatter::SHORT, IntlDateFormatter::SHORT].
So, if for example your locale is set to en_US, then the value would be parsed with an expected format of M/d/yy, h:mm a, which your value wouldn't fit, and hence you'd finally end up with null being set for the entity property.
Make the parser use the proper format
tl;dr
In case the format for the jQuery widget is not being used everywhere in your app, you could for example either temporarily set the proper locale format, or disable locale parsing, like
// for time- or date-only comlumn types you'd use 'time' or 'date' instead of 'datetime'
$dateTimeType = Type::build('datetime')->setLocaleFormat('yyyy/MM/dd HH:mm');
// ...
$intervention = $this->Interventions->patchEntity($intervention, $this->request->data);
// ...
$dateTimeType->setLocaleFormat(null);
or
$dateTimeType = Type::build('datetime')->useLocaleParser(false);
// ...
$intervention = $this->Interventions->patchEntity($intervention, $this->request->data);
// ...
$dateTimeType->useLocaleParser(true);
It should be noted that this will affect all date/time input, not just your starttime and endtime fields!
Should the format used by the jQuery widget on the other hand be the format that you wish to use all the way through your app, then changing the default format could do it too, like
use Cake\I18n\Time;
use Cake\I18n\FrozenTime;
// To affect date-only columns you'd configure `Date` and `FrozenDate`.
// For time-only columns, see the linked SO question below.
Time::setToStringFormat('yyyy/MM/dd HH:mm');
FrozenTime::setToStringFormat('yyyy/MM/dd HH:mm');
in your bootstrap.php. Note that there's also Time/FrozenTime::setJsonEncodeFormat() and Time/FrozenTime::$niceFormat which you may want/need to modify too.
See also
Cookbook > Internationalization & Localization > Parsing Localized Datetime Data
Cookbook > Time > Setting the Default Locale and Format String
CakePHP 3 time column gets date added
Convert the input before marshalling it
Another option would be to for example convert the data to Time instances before the marshalling process. This would avoid possible problems with the previous mentioned solution that would affect all input.
In your InterventionsTable class (could also be put in a behavior or an external listener):
use Cake\Event\Event;
use Cake\I18n\Time;
...
public function beforeMarshal(Event $event, \ArrayObject $data, \ArrayObject $options)
{
foreach (['starttime', 'endtime'] as $key) {
if (isset($data[$key]) && is_string($data[$key])) {
$data[$key] = Time::parseDateTime($data[$key], 'yyyy/MM/dd HH:mm');
}
}
}
See also
Cookbook > Database Access & ORM > Saving Data > Modifying Request Data Before Building Entities

LessThanOrEqual Date without time

I try to validate a Date (not DateTime)
in my validator, i have :
myDate:
- Date: ~
- LessThanOrEqual:
value: today
message: "myDate must be less or equal than today."
Before submitting my form, i send this date to my API (i use symfony as an API with FOSRestBundle):
myDate:"2017-06-09T00:00:00.000Z"
But when i look Symfony\Component\Validator\Constraints\LessThanOrEqualValidator in this method :
protected function compareValues($value1, $value2)
{
return $value1 <= $value2;
}
i have these values:
$value1
DateTime::__set_state(array(
'date' => '2017-06-09 02:00:00.000000',
'timezone_type' => 3,
'timezone' => 'Europe/Paris',
))
$value2
DateTime::__set_state(array(
'date' => '2017-06-09 00:00:00.000000',
'timezone_type' => 3,
'timezone' => 'Europe/Paris',
))
And my validation fails.
Can you help me to solve this problem. I don't need time, i just want to validate the Date. How can i remove the 2 hours ?
Thanks
EDIT :
In my php.ini, i have :
date.timezone ="Europe/Paris"
I solved the problem by sending the right time
First of all LessThanOrEqual do just what its names stands for. It compares if left operand is less or equal to the right operand. No matter if it's a \DateTime or int or something else.
Since you validating \DeteTime i'd suggest you to use Callback Constraint or Expression Constraint so you can define how to validate those. My personal choice for this usecase would be the validation via POST_SUBMIT event in you FormType. See - How to add validators on the fly in Symfony2?

Why are date/time values interpreted incorrectly when patching/saving?

I try to save data from a cakephp 3 form. All data are well saved but datetime not. I've got 2 datetime fields. Those fields are filled by jquery-ui widget.
The problem seems to happened when pacthing entity.
$intervention = $this->Interventions->patchEntity($intervention, $this->request->data);
Debug of $this->request->data :
'user_id' => '1',
'description' => 'test',
'starttime' => '2015/11/15 10:00',
'endtime' => '2015/11/15 12:10'
Debug of my object $intervention after pacthEntity :
object(App\Model\Entity\Intervention)
'id' => (int) 3,
'user_id' => (int) 1,
'description' => 'test',
'starttime' => null,
'endtime' => null
...
starttime and endtime become null and I don't understand why.
Is somebody had this pb before ?
I tried (for debuging and understanding) to force fields value afer patching
and datetime fields in mysql are ok.
$intervention->starttime = date('Y-m-d H:i:s', strtotime($this->request->data['starttime']));
$intervention->endtime = date('Y-m-d H:i:s', strtotime($this->request->data['endtime']));
Thanks for help
Date/time values are being casted/parsed in a locale aware fashion
Update: this is the default behavior with the CakePHP application template versions prior to 3.2.5. As of 3.2.5 locale parsing is not enabled by default anymore, which will make the date/time marshalling logic expect a default format of Y-m-d H:i:s instead.
In the marshalling process, values are being "casted" according to the respective column types. For DATETIME columns, this is done by the \Cake\Database\Type\DateTimeType type class.
To be exact, this is done in \Cake\Database\Type\DateTimeType::marshall().
With the default app template configuration, DateTimeType is configured to use locale aware parsing, and since no default locale format is being set, \Cake\I18n\Time::parseDateTime() will parse the values according to its default "to string format" (Time::$_toStringFormat), which defaults to the locale aware [IntlDateFormatter::SHORT, IntlDateFormatter::SHORT].
So, if for example your locale is set to en_US, then the value would be parsed with an expected format of M/d/yy, h:mm a, which your value wouldn't fit, and hence you'd finally end up with null being set for the entity property.
Make the parser use the proper format
tl;dr
In case the format for the jQuery widget is not being used everywhere in your app, you could for example either temporarily set the proper locale format, or disable locale parsing, like
// for time- or date-only comlumn types you'd use 'time' or 'date' instead of 'datetime'
$dateTimeType = Type::build('datetime')->setLocaleFormat('yyyy/MM/dd HH:mm');
// ...
$intervention = $this->Interventions->patchEntity($intervention, $this->request->data);
// ...
$dateTimeType->setLocaleFormat(null);
or
$dateTimeType = Type::build('datetime')->useLocaleParser(false);
// ...
$intervention = $this->Interventions->patchEntity($intervention, $this->request->data);
// ...
$dateTimeType->useLocaleParser(true);
It should be noted that this will affect all date/time input, not just your starttime and endtime fields!
Should the format used by the jQuery widget on the other hand be the format that you wish to use all the way through your app, then changing the default format could do it too, like
use Cake\I18n\Time;
use Cake\I18n\FrozenTime;
// To affect date-only columns you'd configure `Date` and `FrozenDate`.
// For time-only columns, see the linked SO question below.
Time::setToStringFormat('yyyy/MM/dd HH:mm');
FrozenTime::setToStringFormat('yyyy/MM/dd HH:mm');
in your bootstrap.php. Note that there's also Time/FrozenTime::setJsonEncodeFormat() and Time/FrozenTime::$niceFormat which you may want/need to modify too.
See also
Cookbook > Internationalization & Localization > Parsing Localized Datetime Data
Cookbook > Time > Setting the Default Locale and Format String
CakePHP 3 time column gets date added
Convert the input before marshalling it
Another option would be to for example convert the data to Time instances before the marshalling process. This would avoid possible problems with the previous mentioned solution that would affect all input.
In your InterventionsTable class (could also be put in a behavior or an external listener):
use Cake\Event\Event;
use Cake\I18n\Time;
...
public function beforeMarshal(Event $event, \ArrayObject $data, \ArrayObject $options)
{
foreach (['starttime', 'endtime'] as $key) {
if (isset($data[$key]) && is_string($data[$key])) {
$data[$key] = Time::parseDateTime($data[$key], 'yyyy/MM/dd HH:mm');
}
}
}
See also
Cookbook > Database Access & ORM > Saving Data > Modifying Request Data Before Building Entities

Resources