Fix numeric to bool conversion in converter #7579
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.
A type switch case with multiple conditions causes the value to remain as
interface which causes toBool to always return true for any numeric values. Looking at the code this doesn't seem to be the desired behavior.
This PR treats all non-zero values as true as it seem to have been the intention
of the original code. This is inconsistent compared to conversion from string which uses
strconv.ParseBool
. However, making it consistent would probably break things as the unit tests have test cases for positive values that are greater than 1.Required for all PRs: