Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Typemapping to date property seems to incorrectly convert a timestamp's timezone #413

Open
DnOberon opened this issue Sep 23, 2024 · 1 comment

Comments

@DnOberon
Copy link
Collaborator

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.

image

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.

@browjm4
Copy link
Collaborator

browjm4 commented Sep 23, 2024

timestamps in general have issues in DL and need to be fixed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants