flutter / flutter/devtools

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

Abierto
#4,050 4 comentarios 0 reacciones 0 asignados Ver en GitHub
fix it friday ide: vs-code P3 polish
Lenguaje dominante
Dart
Estrellas
1.7k
Forks
404
Merge medio
6 d 17 h
PR fusionados (30 d)
18

Descripción

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

Guía de contribución

Abrir la guía de contribución

Evaluación

Este issue todavía no se ha evaluado.

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.