Do not use IsoDateTimeConverter to handle DateTimeOffset #2263
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
IsoDateTimeConverter
deserializes aDateTimeOffset
represented according ISO8601 into aDateTimeOffset
with a local offset. For example"1999-01-01T01:01:01.001+05:00"
deserializes to aDateTimeOffset
with a value of01/01/1999 07:01:01 +11:00
. The +11 offset is my local offset (Australia). The default deserialization for aDateTimeOffset
not usingIsoDateTimeConverter
deserializes into aDateTimeOffset
with an offset that reflects the one in the ISO8601 string representation.This seems more appropriate behaviour.
Use
CultureInfo.InvariantCulture
inIsoDateTimeConverter
when deserializingDateTime