Fixed incorrect recognition of data input in chart #4972
Closed
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
The original logic, when processing data such as 12, 23, 34; 230,340,540, the original code will first follow the ";" After splitting, mistakenly taking 12, 23, and 34 as one number for judgment; I made the modifications and will start with ';' After splitting, first perform ',' and then perform int and float judgments to avoid this problem!
Type of Change
Please delete options that are not relevant.
How Has This Been Tested?
I ran locally and tested different situations, such as when the data is one group or multiple groups.
Suggested Checklist: