We found a Contributor License Agreement for you (the sender of this pull request), but were unable to find agreements for all the commit author(s) or Co-authors. If you authored these, maybe you used a different email address in the git commits than was used to sign the CLA (login here to double check)? If these were authored by someone else, then they will need to sign a CLA as well, and confirm that they're okay with these being contributed to Google.
In order to pass this check, please resolve this problem and then comment @googlebot I fixed it.. If the bot doesn't comment, it means it doesn't think anything has changed.

ℹ️ Googlers: Go here for more info.

CLAs look good, thanks!

ℹ️ Googlers: Go here for more info.

It looks like the branch may still out of date, are you sure you have the latest from the master?

It looks like the branch may still out of date, are you sure you have the latest from the master?

There is new updates. Let me update this branch again.

🎉 Congrats!

Thanks again for all the persistence in getting this PR ready. An API like this is tricky to get right. Let's keep an eye on how Flutter developers are using it as it rolls out.

🎉 Congrats!

Thanks again for all the persistence in getting this PR ready. An API like this is tricky to get right. Let's keep an eye on how Flutter developers are using it as it rolls out.

Thank you. I still interested in improve this feature. And I will do that.

Hi there!, thank you for the effort on this project, I have a few questions about TextFormField class and the version of these changes:

1. Has the property:autovalidateMode in the TextFormField class not available anymore?

I did the mistake of upgrade the version I had because the notification on the IDE was really annoying (currently I can't remember the previous version, but after updating the autovalidateMode is not available)...

The current version of flutter I have is the following:

flutter --version

Flutter 1.20.2 • channel stable • https://github.com/flutter/flutter.git
Framework • revision bbfbf1770c (3 weeks ago) • 2020-08-13 08:33:09 -0700
Engine • revision 9d5b21729f
Tools • Dart 2.9.1

flutter doctor

Doctor summary (to see all details, run flutter doctor -v):
[✓] Flutter (Channel stable, 1.20.2, on Mac OS X 10.15.6 19G2021, locale en-HN)
 
[✓] Android toolchain - develop for Android devices (Android SDK version 30.0.1)
[✓] Xcode - develop for iOS and macOS (Xcode 11.5)
[✓] Android Studio (version 4.0)
[✓] IntelliJ IDEA Community Edition (version 2020.2.1)
[✓] VS Code (version 1.48.2)
[✓] Connected device (1 available)

• No issues found!

2. Which version of flutter were these changes merged?

In the changed files I can see that the property autovalidateMode is still present, but in the stable channel using the sdk release: 1.20.2 is not.

Could you give a hand to know what can I do because if not I will refactor the logic of some features already done.

Thanks!

It is not release to stable yet, you can switch to master channel and will be able to use this new API

Oh!, understand it.
ok, thanks.

I couldn't find this autovalidatemode field in the TextFormField.

Following is my flutter doctor output:

`
[√] Flutter (Channel stable, 1.20.4, on Microsoft Windows [Version 10.0.18363.1082], locale en-IN)
• Flutter version 1.20.4 at D:\flutter_windows_1.20.2-stable\flutter
• Framework revision fba99f6 (9 days ago), 2020-09-14 15:32:52 -0700
• Engine revision d1bc06f032
• Dart version 2.9.2

[√] Android toolchain - develop for Android devices (Android SDK version 30.0.2)
• Android SDK at D:\AndroidWork\sdk
• Platform android-30, build-tools 30.0.2
• ANDROID_HOME = D:\AndroidWork\sdk
• Java binary at: C:\Program Files\Android\Android Studio\jre\bin\java
• Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b01)
• All Android licenses accepted.

[√] Android Studio (version 4.0)
• Android Studio at C:\Program Files\Android\Android Studio
• Flutter plugin version 46.0.2
• Dart plugin version 193.7361
• Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b01)

[√] VS Code, 64-bit edition (version 1.48.2)
• VS Code at C:\Program Files\Microsoft VS Code
• Flutter extension version 3.14.1

[√] Connected device (1 available)
• Android SDK built for x86 (mobile) • emulator-5554 • android-x86 • Android 8.1.0 (API 27) (emulator)

• No issues found!
`

When it will be added to stable release?

It is not yet on stable!
I don't know when it will land on stable release.

@EffyCoder & @pedromassango I fixed my issue using autovalidate option, for example, only when the input has focus:

build(BuildContext context) {
  return Container(
    TextFormField(
      autovalidate: focusNode.hasFocus,
    )
  );
}

You can do more stuffs with this approach, and it's working in the same way before it was.

@EffyCoder & @pedromassango I fixed my issue using autovalidate option, for example, only when the input has focus:

build(BuildContext context) {
  return Container(
    TextFormField(
      autovalidate: focusNode.hasFocus,
    )
  );
}

You can do more stuffs with this approach, and it's working in the same way before it was.

Last week I was thinking of adding this feature.

@chunhtai @justinmc My only concern it just that autovalidateMode.hasFocus will only be used on single form fields (FormField, TextFormField, etc..) and not on the Form widget.

We have make it clear that it will have no effect on the Form widget, but this may not be the best thing to do.

Do you have any thing in mind about this?

They can achieve the same result with

return Container(
    TextFormField(
      autovalidateMode: focusNode.hasFocus ?? AutovalidateMode.always :AutovalidateMode.disabled
    )
  );

We should not expend the mode unless there is a mode that cannot be achieve with current API and/or we have a lot of use cases.

I just updated my flutter_form_builder package.

First off, thank you for implementing this feature!!

Why is the type of autovalidateMode dynamic though? Also, my IDE can't find "AutovalidateMode.always" etc

EDIT:
Sorry, just needed to restart my VS CODE