Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix: make android card validation state consistent with iOS #958

Merged
merged 2 commits into from May 23, 2022

Conversation

charliecruzan-stripe
Copy link
Collaborator

Summary

use shouldShowError property to determine if field is actually straight up invalid, or could be valid in the future

Motivation

Fixes #895

Testing

  • I tested this manually
  • I added automated tests

Documentation

Select one:

  • I have added relevant documentation for my changes.
  • This PR does not result in any developer-facing changes.

@charliecruzan-stripe
Copy link
Collaborator Author

tests are fixed on master

@charliecruzan-stripe charliecruzan-stripe force-pushed the charliecruzan-validation-state-android branch from 1ff8b4e to 287b1da Compare May 23, 2022 17:12
@charliecruzan-stripe charliecruzan-stripe merged commit 54569d0 into master May 23, 2022
@charliecruzan-stripe charliecruzan-stripe deleted the charliecruzan-validation-state-android branch May 23, 2022 17:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Inconsistency between Android and iOS on validation state for CardField
1 participant