- Issue created by @vikramsaini1609
- 🇦🇺Australia almunnings Melbourne, 🇦🇺
Might just need to change
$value = $item->value
to$value = $item->date
if its available, and not modify the data - Merge request !118Adding 12 hours to show the same date for all timezones. → (Merged) created by Unnamed author
- 🇦🇺Australia almunnings Melbourne, 🇦🇺
I also dunno about adding 12 hours, whats drupal do?
- 🇦🇺Australia almunnings Melbourne, 🇦🇺
I've flipped this, to not use the field definition, and use the incoming date object as preferred.
Care to test and see if it works as expected now?
- 🇦🇺Australia almunnings Melbourne, 🇦🇺
I'm gonna split out the weird dynamic prop overwrites between the types. Too weird.
This should give some sanity to ✨ Support Smart Date Active to proceed.
- 🇦🇺Australia almunnings Melbourne, 🇦🇺
Moving forward, dates for created/updated should be in UTC.
DateTimes are unaltered coming from Drupal date fields.API change:
Timestamps should now return in UTC.
Date fields should return "as is" in UTC.
Date range fields should return "as is" in UTC.Conversion to local or client time should be a frontend/system concern.
Added tests to DateTest.
Automatically closed - issue fixed for 2 weeks with no activity.