Change "Unicode scalar values" to "Unicode grapheme clusters" in maxLength docs #106275
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.

The current documentation for TextField.maxLength and CupertinoTextField.maxLength suggests that 'character' means "Unicode scalar value", but this is not actually what 'character' means in this context. As described explicitly a little further down on the doc page, and on the page for LengthLimitingTextInputFormatter.maxLength, multiple Unicode scalar values can combine to form one user-perceived character.
This PR corrects the documentation by changing "Unicode scalar values" to "Unicode grapheme clusters", as described in the characters package documentation.
I haven't created a separate issue for this minor docs change; happy to file one if needed.
cc @gspencergoog (as the person git suggests worked on this)
Pre-launch Checklist
I listed at least one issue that this PR fixes in the description above.Hopefully N/A.///).