fix(autocomplete): improve value parsing in AutocompleteTokenField and ListsControl components #4376
+8
−5
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.
All Submissions:
Changes proposed in this Pull Request:
NPPM-2320
The existing parsing strategy with
isNaN( parseInt( key ) )doesn't work if the value is alphanumeric starting with a number. e.g.parseInt( "1a23bc" ) === 1This PR changes the strategy to use the regex pattern
/^\d+$/.test( val.toString() )instead.How to test the changes in this Pull Request:
The issue was identified when testing the component with Mailchimp audiences (not tags or groups)
Other information: