Fix scientific floating point construction represention #1
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.
This PR modifies the library to add decimal point to scientific floating point.
For example:
Now:
3e-5would be written as3e-05With changes:
3e-5would be written as3.0e-05These changes are needed to avoiding reading scientific floating points read as string from
yamlwhich is based onyaml 1.1. yaml 1.1 do not regard this!float 3e-5as floating type. Where asruamel.yamlis based onyaml 1.2which treats them as floatOur requirement is to be able to have a yaml file that is consistent with both both libraries