[4.1][Feature] New Field Type - datetime_picker_localized

[ziming]

It will be great if we can do something like

[
   'name' => 'created_at',
   'type' => 'datetime',
   'timezone' => 'Asia/Country',
],

Then when the created_at column is displayed it is displayed in that country time but in the database the datetime is still in UTC

Same for when creating, updating the record. We specify the datetime in the timezone, then when save, it auto converts to UTC (or the timezone specified in config/app.php)

That will be great

Thank you

[AbbyJanke]

I like the idea of it being customizable, but last i checked it uses the default timezone from laravel config, just set that in constructor or settings? Good to go?

[ziming]

If i set that in config/app.php. It will not save to database in UTC datetime i think but the config datetime timezone

[ziming]

@AbbyJanke Still quite clueless how to do it in constructor such that for viewing is my region time and setting is UTC. Any tips?

[dekmabot]

Also vote for this feature

[tabacitu]

@dekmabot , @ziming currently there are no changes to the datetime value. This makes the field type as unopinionated as possible, I think.

datetime_localized

We could add another field type, datetime_localized, that converts the time with javascript:

• before it’s shown to the user
• before it’s saved in the actual input value

so that the value shown to the user is different from the value in the input (and the value in the db). We could start from the datetime_picker field type, which I believe supports something like this (visible date different from actual input value).

By default it could use the browser’s timezone, and optionally the developer could force a certain timezone.

But this field type would be highly opinionated, and could introduce confusion to the user. A notice or hint should be there in most cases, to tell the user “Pick the date and time in GMT +2 (Europe/Central Europe) timezone.” or something like that.

—

Is this what you guys are looking for?

[ziming]

I think datetime_localized as you suggested would be good. Better if the timezone is shown when the user pick the datetime too :)

[AbbyJanke]

@ziming, i am sure it is on the list but everybody that contributed has full time jobs, backpack is open source and mostly just volunteer work in free time after work, food, sleep and family. PRs always help push things forward but if you want us to do it, give us some time please.

[ziming]

no probs! have a good new year!

[AfzalSabbir]

@ziming you can use model getter setter. Atlease as I've planed.

(I know it's long late)