fix: update value conversion logic in convertValuesToNumbers function #7222
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
Refactored the value conversion logic to handle both numeric and string values more accurately.
dosubot
bot
added
size:XS
github-actions
bot
added
bug
github-actions
bot
added
bug
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's a bug in the
keypairListComponent, for instance, typing "0.8" results in "08" because theconvertValuesToNumbersfunction incorrectly processes "0." as a number and removes the decimal point.To fix this, I updated the logic so that any input matching the pattern
"(any number)."is treated as a string rather than a number. If the input follows the pattern"(any number).(any number)", it will be correctly converted to a number.This ensures that decimal values are preserved during input.