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
Without having looked at the code, it's probably truncating to the last non-zero digit (or to the nearest digit triple - millis, micros, etc). Since the amount is/should be exact, there's no information lost here.
The underlying Utf8JsonWriter writes DateTime and DateTimeOffset instances according to the extended ISO 8601 profile (not roundtrippable "O", which is too strict on deserialization). Trailing second fraction zeros are omitted, so the writer produces the smallest output required to roundtrip. See some test data showing how the writer trims.
Activity
Clockwork-Muse commentedon Dec 5, 2019
Without having looked at the code, it's probably truncating to the last non-zero digit (or to the nearest digit triple - millis, micros, etc). Since the amount is/should be exact, there's no information lost here.
layomia commentedon Dec 5, 2019
The underlying
Utf8JsonWriterwrites DateTime and DateTimeOffset instances according to the extended ISO 8601 profile (not roundtrippable "O", which is too strict on deserialization). Trailing second fraction zeros are omitted, so the writer produces the smallest output required to roundtrip. See some test data showing how the writer trims.I've filed an issue to add this information to the official docs: dotnet/docs#16128.