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

[BUG] matchField does not re-evaluate when the other field is changed #89

Open
manstie opened this issue Aug 7, 2022 · 0 comments
Open
Assignees
Labels
bug Something isn't working

Comments

@manstie
Copy link

manstie commented Aug 7, 2022

Describe the bug
When using matchField, if you enter a value into the field with the validator it will be marked as invalid, and then when you match the value in the field without the validator it stays invalid.

To Reproduce
Steps to reproduce the behavior:

  1. Create basic match field as per docs
  2. Type 'password' into the passwordConfirmation field
  3. Type 'password' into the password field
  4. The passwordConfirmation field is still invalid

Expected behavior
When the first field obtains a value which is the same as the field with the validator, the field should be marked as valid.

@manstie manstie added the bug Something isn't working label Aug 7, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants