fix: Updating Email.pure to Email.dirty in flutter_form_validation example #3973
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.
fix: MyFormBloc Email and Password validation
fix: Removing redundant FormzInputs
Status
READY
Breaking Changes
NO
Description
In the flutter_form_validation we have this method
As you can see we're passing Email.pure instead of Email.dirty to the email field in the MyFormState. After changing pure to dirty, I realized that it was redundant having email.isValid since Email.dirty does automatic validation for that input so I took it out. Now we only have:
Same thing applied to the
_onPasswordChanged
method. Targets #3972Type of Change