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
I suggest that we take the opportunity with D2 to fix some anomalies with date/time pickers in D1.
My time zone is GMT+1.
If I configure a D1 Text Input node in Time Picker mode and select a time of 12:00 it passes on the number 39600000 which is 11 hours in milliseconds. It is taking the timezone into account.
If I configure a D1 Time Picker Form field, however, and enter 12:00 it provides the string "1970-01-01T11:00:00.000Z".
Whether either of these is ideal I am not sure. Personally I think I would prefer 12 hours in milliseconds, whatever the timezone.
This flow might be useful if others want to see the behaviour
Closing this as the date, time, and datetime pickers all generate text strings, so the issue described does not occur. In my opinion this is an improvement over the D1 technique.
I suggest that we take the opportunity with D2 to fix some anomalies with date/time pickers in D1.
My time zone is GMT+1.
If I configure a D1 Text Input node in Time Picker mode and select a time of 12:00 it passes on the number 39600000 which is 11 hours in milliseconds. It is taking the timezone into account.
If I configure a D1 Time Picker Form field, however, and enter 12:00 it provides the string "1970-01-01T11:00:00.000Z".
Whether either of these is ideal I am not sure. Personally I think I would prefer 12 hours in milliseconds, whatever the timezone.
This flow might be useful if others want to see the behaviour
I think there are also anomalies with the Date pickers in D1, but I have not fully analysed those yet.
The text was updated successfully, but these errors were encountered: