I have made use of the widget in a form field when a user is registering for a new account like so

class PasswordValidator extends StatelessWidget {
  final TextEditingController controller;
  final Function() onSuccess;
  const PasswordValidator({
    Key? key,
    required this.controller,
    required this.onSuccess,
  }) : super(key: key);

  @override
  Widget build(BuildContext context) {
    return Padding(
      padding: const EdgeInsets.only(
        left: 20.0,
        top: 0.0,
        right: 20.0,
        bottom: 20.0,
      ),
      child: FlutterPwValidator(
        width: MediaQuery.of(context).size.width,
        height: MediaQuery.of(context).size.height * 0.2,
        minLength: 6,
        specialCharCount: 1,
        uppercaseCharCount: 1,
        numericCharCount: 1,
        onSuccess: onSuccess,
        controller: controller,
      ),
    );
  }
}

During the API call, I set the page to be replaced with a ProgressIndicator. When the API calls fails, the user is kept on the same page and the ProgressIndicator is removed and text form fields are reset, in resetting the controller value that the password field is bound to, the following error is thrown

The following assertion was thrown while dispatching notifications for TextEditingController:
setState() called after dispose(): _FlutterPwValidatorState#85b38(lifecycle state: defunct, not mounted)

This error happens if you call setState() on a State object for a widget that no longer appears in the widget tree (e.g., whose parent widget no longer includes the widget in its build). This error can occur when code calls setState() from a timer or an animation callback.

The above error is also thrown anytime the password field is tapped or interacted with at all.

I needed a simple validation of the number of letters the component did not have this functionality.

I implemented it if you think it's interesting to keep in the project follow the PR.

I have implemented the PW Validator and I am getting this error with every letter typed into the password field

======== Exception caught by foundation library ==================================================== The following assertion was thrown while dispatching notifications for TextEditingController: setState() called after dispose(): _FlutterPwValidatorState#095a5(lifecycle state: defunct, not mounted)

This error happens if you call setState() on a State object for a widget that no longer appears in the widget tree (e.g., whose parent widget no longer includes the widget in its build). This error can occur when code calls setState() from a timer or an animation callback.

I tried so hard to add a key attribute to your code, but it didn't work out I want a key attribute so I can access the validate function when I press my register button, so it won't be greyed out when I press register if he didn't type a password correctly

Hi there,

I added the possiblity to give our own FlutterPwValidatorStrings as discussed in https://github.com/ArefMozafari/flutter_pw_validator/issues/9

Tell me if I need to change a few things. Thanks!

Hi there,

As every year in october, Hacktoberfest has started! :-) More details here : https://hacktoberfest.digitalocean.com/resources/maintainers Would you add the hacktoberfest label to your repo so contributors know they can participate and fix issues/craft PRs?

Thanks a lot.

Hey there!

It would be awesome if we could provide translation for hints. I can craft a PR, is this OK for you?

I was thinking of renaming the Strings Class by a FlutterPwValidatorStrings and allowing to optionaly pass it to the FlutterPwValidator widget with a strings params. If not provided, use the default one.

Thanks alot!

Hey there. Thanks for this cool pub ! :-)

On your pub.dev page, the issue link is broken. I fixed it, you'll need to republish for changes to be applied.

Why are width and height required? For a project I am working on it would be way more comfortable if the width and height would be automatically adjusted to the available space. Parameters like the height of the Validationbar, Paddings, TextSize etc could be passed in from the outside but have a sensible default.

Would you be open if I will open up a PR soon removing the fixed width and height?

Description: The documnentation score of the package is 10/20 which can be improved by using documentation comments instead of normal comments

Screenshot:

- Normal Comment: //
- Documentation Comment: ///

Disposing the TextEditingController should be done by the one who created the controller.

If it is disposed in the place where it was created it will lead to the following Error instead:

The following assertion was thrown while finalizing the widget tree:
A TextEditingController was used after being disposed.

Once you have called dispose() on a TextEditingController, it can no longer be used.
When the exception was thrown, this was the stack: 

Moreover it might be that the TextEditingController is still needed even after the FlutterPWValidator is no longer needed

Sharing an example where I have both Email and password and for a better user experience, I want to be able to show a password validator only when someone starts to type the password.

Moreover, is there a way to shift the validator to align perfectly under the field ?

It's good and super cool to be able to use the password validator at signup or while changing it from UI. However, I am wondering if there is a similar way I could enforce rules while resetting passwords coming from Firebase.