Fix - Type System.Decimal
loses precision during serialization and deserialization when the value contains floating-point digits
#10
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.
Summary
This pull request addresses the issue where the
System.Decimal
type loses precision during serialization and deserialization when the value contains floating-point digits.Problem
When serializing and deserializing
System.Decimal
values, especially those with floating-point digits, there is a noticeable loss of precision. This can lead to incorrect values being processed in applications that rely on precise decimal calculations.Reproduction
System.Decimal::MaxValue
by 10.ConvertTo-Metadata
.ConvertFrom-Metadata
.Solution
System.Decimal
value. This ensures that during deserialization, the value is correctly interpreted as aSystem.Decimal
and not mistakenly as aSystem.Double
.Example
Links
System.Decimal
loses precision during serialization and deserialization when the value contains floating-point digits #9