[Breaking Change] Use maxLengthEnforcement instead of maxLengthEnforced

[Alex Li]

Hello everyone,

If you don't use the maxLength or maxLengthEnforced properties in a TextField, TextFormField, or CupertinoTextField, or don't care about the truncation behavior of an editable text field, you can stop reading.

To control the behavior of maxLength in the LengthLimitingTextInputFormatter, use maxLengthEnforcement instead of maxLengthEnforced, which was deprecated.

There are multiple text editing behaviors while the user is entering different types of characters, using different keyboards. To separate behaviors and respect different input traditions for different platforms and users, we recently brought a new tri-stage enum named MaxLengthEnforcement for the LengthLimitingTextInputFormatter, also applied to editable text fields.

For more details about how to migrate or relevant changes to flutter, see links below.

The migration guide: https://flutter.dev/docs/release/breaking-changes/use-maxLengthEnforcement-instead-of-maxLengthEnforced

The design doc: https://docs.google.com/document/d/1S900lQaTPOsePnIeE7o3-Ia8f39VZaSv0JnjNyBfCvU

The PR: https://github.com/flutter/flutter/pull/68086

Feel free to comment on the PR if you have any questions.

Thanks,

Alex Li