Specify that widget rebuilds is only available when running in debug-mode
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 74/100
Research direction
Start in the performance panel code that renders the disabled widget-rebuild checkbox and the "To see widget rebuilds" text; trace how it handles the trackRebuildDirtyWidgets service extension and the debugOnRebuildDirtyWidget limitation described in packages/flutter/lib/src/widgets/debug.dart. Done means profile-mode frames show the specified unavailability message without a checkbox, while debug-mode behavior remains usable.
Written by the indexing model from the issue text.
Description
Currently when you run your app in profile-mode, the performance panel shows a disabled checkbox that makes it seem like it should be possible to "count widget builds" (see screenshot below)
In actuality, "count widget builds" relies on the trackRebuildDirtyWidgets service extension, which uses debugOnRebuildDirtyWidget. This is only available in debug-mode: https://github.com/flutter/flutter/blob/f9e809913240552c391bf31b1cfdbdf410224d8c/packages/flutter/lib/src/widgets/debug.dart#L59
Instead of "To see widget rebuilds for Flutter frames, enable CountWidgetRebuilds", we should remove the checkbox and update the text to say "Rebuild information not available for this frame. Widget rebuild counts are only available when running an app in debug-mode."
- Dominant language
- Dart
- Stars
- 1.7k
- Forks
- 405
- Avg merge
- 4d 23h
- Merged PRs (30d)
- 12
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from flutter/devtools
-
cleanup P1
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
-
a: quality cost: low P2
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
contributions welcome cross-screen inspector-2.0-polish P2
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
-
cross-screen P3
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
documentation good first issue P2
Difficulty 1/5 Under an hour Newbie friendliness 88/100
All issues in flutter/devtools
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
code quality good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Suwayomi/Suwayomi-Tsumiru#479 ·
-
Build Failure: agora_rtc_engine compiled against android-31 while dependencies require android-34+ Open
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 92/100
conceptadev/noir#95 ·