Repository navigation
Some fields do not require validation #86
Description
Activity
have similar use case, currently using your example, but I don't think it's the good way because we still create the error enum.
I wrote a wrapper for this case:
class UnirequiredInput<T> extends FormzInput<T?, void> { const UnirequiredInput.pure() : super.pure(null); const UnirequiredInput.dirty({T? value}) : super.dirty(value); @override void validator(T? value) {} }
But this is just a workaround
Reacted by Robson Silva, Jens Becker and Bartosz
Every time a FormZInput is defined we must add a validation error even if we never get to use it. Some fields do not require validation, but do require being inside the form to later verify if the field has changed its value.
Example: