Fixes JSON down converter decimal spec issue. #134
Merged
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.
Description:
Ion allows
2.d-1
indicating0.2
while JSON doesn't. When IonDoNet JSON downconverter converts2.d-1
to JSON decimal, it returns2.e-1
which is an invalid JSON decimal since exponente
can't follow.
directly. Refer to JSON spec for more details.So IonDotNet JSON down converter should return a valid JSON decimal (e.g.
2e-1
).By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.