Skip to content

Add breaking change page for DropdownButton enabled property - #13430

Merged
sfshaza2 merged 9 commits into
flutter:mainfrom
Mairramer:docs/dropdownbutton-enabled
Jun 2, 2026
Merged

sfshaza2 merged 9 commits into
flutter:mainfrom
Mairramer:docs/dropdownbutton-enabled

Conversation

@Mairramer

Copy link
Copy Markdown
Contributor

Description of what this PR is changing or adding, and why:
Adds a breaking change page for the new enabled property logic on DropdownButton and DropdownButtonFormField. This explains why the onChanged callback is no longer required and clarifies the fallback behavior for backward compatibility. It also guides developers on how to properly separate interactive state (enabled) from widget behavior (onChanged), highlighting what the dart fix covers and what requires manual migration (like conditional logic).

Issues fixed by this PR (if any):
N/A but related to flutter/flutter#57953

PRs or commits this PR depends on (if any):
Depends on flutter/flutter#182419

Presubmit checklist

  • If you are unwilling, or unable, to sign the CLA, even for a tiny, one-word PR, please file an issue instead of a PR.
  • If this PR is not meant to land until a future stable release, mark it as draft with an explanation.
  • This PR follows the Google Developer Documentation Style Guidelines—for example, it doesn't use i.e. or e.g., and it avoids I and we (first-person pronouns).
  • This PR uses semantic line breaks
    of 80 characters or fewer.

@Mairramer
Mairramer requested review from a team and sfshaza2 as code owners May 27, 2026 12:34

@gemini-code-assist gemini-code-assist Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request documents a breaking change introducing the enabled property and making the onChanged callback optional for DropdownButton and DropdownButtonFormField. The feedback focuses on improving the documentation quality by adhering to style guidelines (avoiding first-person pronouns and abbreviations like 'i.e.'), wrapping lines to respect an 80-character limit, and ensuring consistent link text that matches the page title.

Mairramer and others added 5 commits May 27, 2026 09:36
…-enabled-property.md

Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>
…-enabled-property.md

Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>
…-enabled-property.md

Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>
…-enabled-property.md

Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>
…optional enabled property and onChanged callback
@sfshaza2
sfshaza2 requested a review from justinmc May 28, 2026 18:35
@sfshaza2

Copy link
Copy Markdown
Contributor

@justinmc, can you either review or delegate?

@sfshaza2

Copy link
Copy Markdown
Contributor

/gcbrun

@flutter-website-bot

flutter-website-bot commented May 28, 2026 •

Copy link
Copy Markdown
Collaborator

@justinmc justinmc left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM 👍 . Thanks for your hard work on this feature @Mairramer!

@sfshaza2

Copy link
Copy Markdown
Contributor

Thanks for your review, @justinmc! @Mairramer, can you address Justin's final nits so I can land? Thx!

@Mairramer

Copy link
Copy Markdown
Contributor Author

I’ve now formatted it using the proofread_markdown skill.

@parlough

parlough commented Jun 1, 2026

Copy link
Copy Markdown
Member

/gcbrun

@sfshaza2 sfshaza2 left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm

@sfshaza2
sfshaza2 merged commit 95c4391 into flutter:main Jun 2, 2026
12 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants