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
Fix conversion from standard Date to Time & DateTime
Time zone offset was not converted correctly. Offset exposed by the
standard JavaScript `Date` is the difference, in minutes, from local
time to UTC. So positive offset means local time is behind UTC and
negative means it's ahead. This is different from Neo4j temporal types
that support time zone offsets - `Time` and `DateTime`. They define
offset as the difference, in seconds, from UTC to local time. Previous
code converted offset in minutes to offset in seconds but did not
change the sign of the value.
* @param {Integer|number} minute the minute for the new date-time.
313
314
* @param {Integer|number} second the second for the new date-time.
314
315
* @param {Integer|number} nanosecond the nanosecond for the new date-time.
315
-
* @param {Integer|number|null} timeZoneOffsetSeconds the total time zone offset in seconds for the new date-time. Either this argument or `timeZoneId` should be defined.
316
+
* @param {Integer|number} timeZoneOffsetSeconds the time zone offset in seconds. Either this argument or `timeZoneId` should be defined.
317
+
* Value represents the difference, in seconds, from UTC to local time.
318
+
* This is different from standard JavaScript `Date.getTimezoneOffset()` which is the difference, in minutes, from local time to UTC.
316
319
* @param {string|null} timeZoneId the time zone id for the new date-time. Either this argument or `timeZoneOffsetSeconds` should be defined.
0 commit comments