)]}'
{
  "commit": "b63b216792392f6236c222f87456044ffde973b9",
  "tree": "6b81cd3c3bac1c4651f5f584bcf8b77c8a58171d",
  "parents": [
    "b2977965ce7c5d75a99ec050ca2f5094d6ea5dec"
  ],
  "author": {
    "name": "Mohanad Abdallah",
    "email": "55765052+MohanadAbdallah-mv@users.noreply.github.com",
    "time": "Tue Sep 29 23:18:59 2026 +0000"
  },
  "committer": {
    "name": "GitHub",
    "email": "noreply@github.com",
    "time": "Tue Sep 29 23:18:59 2026 +0000"
  },
  "message": "Rename \"subtext\" to \"supportingTextPadding\" in `FormField`\u0027s documentation (#183582)\n\n**Maintainer\u0027s note:** This PR was originally named \"Adding\nsupportingTextPadding to InputDecorator and InputDecorationTheme\", and\nhas been split into two parts due to decoupling. The majority of the\nchange is now applied by https://github.com/flutter/packages/pull/12769\n. This PR only addresses the terminology change, since we discovered\nthat the M3 spec (https://m3.material.io/components/text-fields/specs )\nofficially refers to error text and hint text as \"supporting text\".\n\n-----\n\nThis PR introduces the `supportingTextPadding` property to\n`InputDecorator`, `InputDecoration`, and `InputDecorationThemeData`.\nWhile originally conceived as `errorPadding`, this property was renamed\nto `supportingTextPadding` during review to align with the Material\nDesign 3 specification, as it controls the padding for the entire\nsupporting text row (which includes helper text, error text, and counter\nwidgets).\nAdditionally, this PR addresses layout, intrinsic sizing, and code\nconsistency concerns raised during the review process:\n#### Key Features \u0026 Refactors:\n1. **Added `supportingTextPadding`:** Allows complete, independent\ncontrol over the padding of the supporting text row\n(helper/error/counter).\n2. **Decoupled Layout Constraints:** Introduced\n`supportingTextConstraints` in `_layout()` to bound the supporting text\nrow independently of `contentConstraints`, ensuring custom paddings do\nnot break or shift the layout of inline `prefix`/`suffix` widgets.\n3. **Fixed Intrinsic Height Mismatches:** Corrected\n`computeMinIntrinsicHeight()` to compute `supportingTextWidth`\nseparately from the primary width deflation path, ensuring intrinsic\nheight calculations accurately predict wrapped text heights.\n4. **Unified Terminology:** Renamed all legacy internal `subtext`\nreferences (e.g. `_SubtextSize`, `_computeSubtextSizes`,\n`subtextHeight`) to `supportingText` to match the public property name\nand the M3 spec.\n\n\n*List which issues are fixed by this PR. You must list at least one\nissue. An issue is not required if the PR fixes something trivial like a\ntypo.*\nFixes #175834 \n\n## Pre-launch Checklist\n\n- [x] I read the [Contributor Guide] and followed the process outlined\nthere for submitting PRs.\n- [x] I read the [AI contribution guidelines] and understand my\nresponsibilities, or I am not using AI tools.\n- [x] I read the [Tree Hygiene] wiki page, which explains my\nresponsibilities.\n- [x] I read and followed the [Flutter Style Guide], including [Features\nwe expect every widget to implement].\n- [x] I signed the [CLA].\n- [x] I listed at least one issue that this PR fixes in the description\nabove.\n- [x] I updated/added relevant documentation (doc comments with `///`).\n- [x] I added new tests to check the change I am making, or this PR is\n[test-exempt].\n- [ ] I followed the [breaking change policy] and added [Data Driven\nFixes] where supported.\n- [ ] All existing and new tests are passing.\n\nIf you need help, consider asking for advice on the #hackers-new channel\non [Discord].\n\n**Note**: The Flutter team is currently trialing the use of [Gemini Code\nAssist for\nGitHub](https://developers.google.com/gemini-code-assist/docs/review-github-code).\nComments from the `gemini-code-assist` bot should not be taken as\nauthoritative feedback from the Flutter team. If you find its comments\nuseful you can update your code accordingly, but if you are unsure or\ndisagree with the feedback, please feel free to wait for a Flutter team\nmember\u0027s review for guidance on which automated comments should be\naddressed.\n\n\u003c!-- Links --\u003e\n[Contributor Guide]:\nhttps://github.com/flutter/flutter/blob/main/docs/contributing/Tree-hygiene.md#overview\n[AI contribution guidelines]:\nhttps://github.com/flutter/flutter/blob/main/docs/contributing/Tree-hygiene.md#ai-contribution-guidelines\n[Tree Hygiene]:\nhttps://github.com/flutter/flutter/blob/main/docs/contributing/Tree-hygiene.md\n[test-exempt]:\nhttps://github.com/flutter/flutter/blob/main/docs/contributing/Tree-hygiene.md#tests\n[Flutter Style Guide]:\nhttps://github.com/flutter/flutter/blob/main/docs/contributing/Style-guide-for-Flutter-repo.md\n[Features we expect every widget to implement]:\nhttps://github.com/flutter/flutter/blob/main/docs/contributing/Style-guide-for-Flutter-repo.md#features-we-expect-every-widget-to-implement\n[CLA]: https://cla.developers.google.com/\n[flutter/tests]: https://github.com/flutter/tests\n[breaking change policy]:\nhttps://github.com/flutter/flutter/blob/main/docs/contributing/Tree-hygiene.md#handling-breaking-changes\n[Discord]:\nhttps://github.com/flutter/flutter/blob/main/docs/contributing/Chat.md\n[Data Driven Fixes]:\nhttps://github.com/flutter/flutter/blob/main/docs/contributing/Data-driven-Fixes.md\n\n---------\n\nCo-authored-by: Tong Mu \u003cdkwingsmt@users.noreply.github.com\u003e",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "4c231d1ff306364bebf1491679d0a2c1eb8da750",
      "old_mode": 33188,
      "old_path": "packages/flutter/lib/src/widgets/form.dart",
      "new_id": "0d841b3699b5a6293e8282c5757d08cb7c3fe515",
      "new_mode": 33188,
      "new_path": "packages/flutter/lib/src/widgets/form.dart"
    }
  ]
}