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
From what I've looked at this seems like a bug, but I may be misusing the typemapping system. When I typemap a property as a date type, and don't provide a date format string, the UTC timestamp I give gets changed by 6 hours. It seems like timezone conversion, but I import UTC dates, and by not providing the timestamp string it should be assumed as UTC time.
Steps to Reproduce
Import data like this "StartDate": "2021-10-04T07:00:00.000Z" and create a node from it using a date type and don't give a timestamp string. When you query the node, you will see the date is now "StartDate": "2021-10-04T01:00:00.000Z".
Impact
Data seems to be changing when it shouldn't.
The text was updated successfully, but these errors were encountered:
Bug Description
From what I've looked at this seems like a bug, but I may be misusing the typemapping system. When I typemap a property as a date type, and don't provide a date format string, the UTC timestamp I give gets changed by 6 hours. It seems like timezone conversion, but I import UTC dates, and by not providing the timestamp string it should be assumed as UTC time.
Steps to Reproduce
Import data like this "StartDate": "2021-10-04T07:00:00.000Z" and create a node from it using a date type and don't give a timestamp string. When you query the node, you will see the date is now "StartDate": "2021-10-04T01:00:00.000Z".
Impact
Data seems to be changing when it shouldn't.
The text was updated successfully, but these errors were encountered: