DateTime scalar doesn't keep the offset in @DgsMutation

[albertogdd]

In any given query/mutation, when we send this value for a scalar DateTime attribute:

"date": "2021-07-12T11:30:00.00+02:00"

It gets parsed to OffsetDateTime in the ExtendedScalars implementation nicely, but later on something happens before getting into @DgsMutation, where the date is updated to UTC:

"date": "2021-07-12T09:30:00Z"

This didn't happened to us with kickstart-graphql, is it a bug in DGS? Or are we doing something wrong

We want to validate the date offset received, but as it is now, it gets always updated to UTC automatically, hence we can't know the offset sent.

[StefanHaunsberger]

We do not have to use this DateTime scalar, we can also use our own one if that works better?

[albertogdd]

ExtendedScalars doesn't seem to be the issue as the OffsetDateTime generated there contains the correct offset.

[albertogdd]

We tested also using our own custom DateTime scalar and happens the same

[StefanHaunsberger]

Should we report this to the official Netflix GitHub issues?

[paulbakker]

We'll look into it, just didn't get to it yet.

[berngp]

@StefanHaunsberger is this happening with the latest version? I created a small test to assert what you mention and haven't been able to replicate. ref #506

[albertogdd]

@berngp Sorry for the late reply. Apparently this used to happen with earlier versions, but at some point it got fixed and now works fine, thank you for the effort!