flutter / flutter/devtools

Improve UX when features aren't supported in the current run-mode

Offen
#4,050 4 Kommentare 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen
fix it friday ide: vs-code P3 polish
Vorherrschende Sprache
Dart
Sterne
1.7k
Forks
404
Ø Merge
6 T. 17 Std.
Gemergte PRs (30 T.)
18

Beschreibung

It's not clear what DevTools the user is allowed to open and when. For example, if a user is running in profile mode and tries to run the "Open Widget Inspector" command in VSCode they are shown this screen:

Screen Shot 2022-04-27 at 12 54 48 PM

It seems like that most things are supported in Debug and Profile mode, but show inconsistent messages:

| | Debug | Profile | Release |
|---|---|---|---|
| Widget Inspector | 🟢 | 🔴 | 🔴 |
| CPU Profiler | 🔴 | 🟢 | 🔴 |
| Memory Page | 🟡 | 🟢 | 🔴 |
| Performance Page | 🔴 | 🟢 | 🔴 |
| Network Page | 🟢 | 🟢 | 🔴 |
| Logging Page | 🟢 | 🟢 | 🔴 |

For example, when running in debug mode, the toast messages for the CPU Profiler, Memory, and Performances pages are inconsistent. The memory page displays a warning but the CPU Profiler and Performance pages display an error:

Screen Shot 2022-04-27 at 2 05 46 PM

Screen Shot 2022-04-27 at 2 08 35 PM

If you try to open a DevTools panel in release mode, you get a warning like this, but I'm also wondering if we could clarify this message:

Screen Shot 2022-04-27 at 2 06 48 PM

cc: @kenzieschmoll @DanTup

Beitragsleitfaden

Beitragsleitfaden öffnen

Bewertung

Dieses Issue wurde noch nicht bewertet.

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.