This repository was archived by the owner on Dec 24, 2022. It is now read-only.
JsonSerializer/JsvTypeSerializer inconsistently uses the AssumeUtc config setting #505
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.
DateTime handling is inconsistent with respect to the
AssumcUtcwhen using theJSConfigsetting.If serializing to JSON - The
JsonTypeSerializerwill use the UTC specification type and convertUnspecifiedDateTime values to UTC in methodWriteWcfJsonDateIf serializing to CSV- The
JsvTypeSerializerwill not use the UTC specification type and does not convertUnspecifiedDateTime values to UTC in methodToShortestXsdDateTimeStringAdding an internal extension method
UseConfigSpecifiedSettingto match DateTime conversion between the two different serializers.