fix: numeric type evolution #126
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
louis-bompart
requested changes
Apr 12, 2022
src/fieldAnalyser/typeUtils.spec.ts
Outdated
| { | ||
| from: FieldTypes.STRING, | ||
| to: FieldTypes.LONG, | ||
| }, | ||
| ])('should return true', ({from, to}) => { |
There was a problem hiding this comment.
'should return true'? 
olamothe
approved these changes
Apr 13, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
There was an issue with the numeric type "evolution".
When the FieldAnalyser was detecting that a field that was previously defined as Integer but now detected as float, then the more englobing type (float) was chosen.
However, the opposite scenario was causing an issue rather than sticking to the most englobing type.