feat: Add validation state to CardField (#423) #629
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.
Closes #423
This adds three new fields to the card details returned by
onCardChange
:validCVC
,validExpiryDate
, andvalidNumber
. On iOS, each field has a possible value of "Valid", "Invalid", "Incomplete", and "Unknown". The Android SDK doesn't seem to expose whether a field is incomplete or not, so Android has "Valid", "Invalid", and "Unknown".This is my first time working on a native module so I'm not 100% on the Swift and Kotlin syntax, let me know if there's a better way to write this and I'll update it