You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Handle Timezones In DateTime Display/Posting Layers:
We need to ensure that we always account for timezones when working with date/time/datetime to ensure internationalization compatibility. The trick here is to know both local time and international time, to ensure we don't loose meta information, for example: when setting flight times we need to know the local time in order to determine day/night hours.
To this point we should remove "date" and "time" type fields and only support "datetime" fields.
Maybe we should introduce some additional settings for datetime fields, like: explicit-timezone which will force users to set a timezone.
The text was updated successfully, but these errors were encountered:
Handle Timezones In DateTime Display/Posting Layers:
We need to ensure that we always account for timezones when working with date/time/datetime to ensure internationalization compatibility. The trick here is to know both local time and international time, to ensure we don't loose meta information, for example: when setting flight times we need to know the local time in order to determine day/night hours.
To this point we should remove "date" and "time" type fields and only support "datetime" fields.
Maybe we should introduce some additional settings for datetime fields, like: explicit-timezone which will force users to set a timezone.
The text was updated successfully, but these errors were encountered: