Make Debug Console REPL have different Requests & Request response settings
Nadie ha tomado este issue todavía.
Evaluación
Este issue todavía no se ha evaluado.
Descripción
Right now, any input into the debug console that's handled by the debug adapter, triggers an entire new update chain. This should be customizable.
If a debug adapter is viewing a large scope, and a debugger "power user" want's to input something into the debug console, for whatever reason, perhaps access/perform commands that can't / shouldn't be / isn't suitable to be shown in the UI, it will trigger an update chain - re-requesting all the data that is displayed, which can be quite a bit. This is a burden for the end-user, as they will have to remember to "close" all scopes before entering any input.
Solution:
Make the requests the debug console handles (evaluateRequest) customizable by being able to set a field on the response object "doNotUpdate" or something like that. I think you're getting what I am aiming for here.
- Lenguaje dominante
- HTML
- Estrellas
- 1.8k
- Forks
- 173
- Merge medio
- 7 d 7 h
- PR fusionados (30 d)
- 2
Preparar el entorno
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de microsoft/debug-adapter-protocol
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 68/100
-
Dificultad 5/5 Más de una semana Aptitud para principiantes 35/100
microsoft/debug-adapter-protocol#633 · 1 comentario ·
-
Dificultad 4/5 3-5 días Aptitud para principiantes 42/100
-
Dificultad 5/5 Más de una semana Aptitud para principiantes 35/100
microsoft/debug-adapter-protocol#599 · 8 reacciones ·
-
under-discussion
Dificultad 2/5 1-3 horas Aptitud para principiantes 48/100
microsoft/debug-adapter-protocol#596 · 9 comentarios ·