Best practice for to create a validation that needs a value at run-time #16
Description
I'm migrating to the 1.0 version of the library and I'm a bit stuck. I have a couple of validations that previously used inline validations. For example, I have a form that requires the user to enter the email twice and compare to make sure they are the same. It appears that I may need to follow the pattern setup with PasswordFormField and create a custom Form Field and a custom Validatable. That seems like a lot of work.
Am I missing something?