[Issue-1146] Fix CardField validation problem on Android #1213
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.
Issue: #1146
Order of react props apply is not as expected:
setCountryCode applied first, then setPostalCodeEnabled. As postalCodeEnabled is true by default, it leads to issues with postalCodeEnabled={false} on react side.
Summary
Safely change
mCardWidget.postalCodeRequired = false
whenpostalCodeEnabled={false}
Motivation
For some reason, react props are applied to Android native element in unexpected order (countryCode first, then postalCodeEnabled), which in conjunction with default value of
polstalCodeEnabled === true
leads to non-workingCardField
on Android withpostalCodeEnabled={false}
Testing
Documentation
Select one: