Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

Where is the Documentation for VSCode's Debug Adapter and Protocol implementation?

Abierto
  • ¿Algo no está bien?
#450 1 comentario 5 reacciones 0 asignados Ver en GitHub

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
30/100
Tipo de issue
Documentación
Claridad
Bastante claro
Estado de actividad
Estancado
Stack tecnológico
typescript, vscode
Área
developer-experience, documentation, tooling

Línea de trabajo

Comienza con la Debugger Extension Guide, la DAP specification, la VS Code API Reference y VS Code Mock Debug; después, inspecciona los archivos referenciados debugProtocol.ts y loggingDebugSession.ts. Compara sus descripciones con las release notes de breakpointLocations y la discusión citada del issue. Se considera terminado cuando se añada contexto oficial que explique los propósitos de las capacidades, el comportamiento visible para el usuario y las opciones y el mecanismo de LoggingDebugSession.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

feature-request

I’ve been trying to work my way through Debugger Extension documentation to improve an existing debugger extension. My resources so far have been:

  1. Debugger Extension Guide
  2. Debug Adapter Protocol Overview
  3. Debug Adapter Protocol Specification
  4. VS Code API Reference
  5. VS Code Mock Debug

I would love to add "Documentation for VS Code's DAP Implementation" to that list, but I have unfortunately not been able to find it. The best I've found is using JSDoc-driven IntelliSense on this package, but that has been less helpful than expected.

When attempting to determine how to map DAP Capabilities to the debugger I'm integrating, it helps to have a good understanding of how VS Code is going to use a feature.

One good example would be the supportsBreakpointLocationRequest capability. Here is its JSDoc comment in its entirety:

The debug adapter supports the breakpointLocations request.

Okay... that sounds like a DAP reference. Let's look at what the specification has to say about BreakpointLocations Requests:

The breakpointLocations request returns all possible locations for source breakpoints in a given range.

At this point I'm still confused. Looking at the members of the related BreakpointLocationsArguments type provides a bit of insight, but it doesn't definitively help me understand what the purpose of this capability is...

A web search for related keywords finally turns up something helpful:

Finding possible breakpoints in a source range

The new breakpointLocations request can be used by a DAP client to find all possible breakpoint locations in a given source range. This can be used in the UI in order to improve the discoverability of "inline" ("column") breakpoints.

Ahh! This is how we enable column breakpoints! Got it! That helpful context was provided in VS Code release notes from September 2019...

Would it be possible to add this to some official documentation, whether that be in the DAP Specification or VS Code's specific implementation, or both?

Other examples that I've contended (or am still contending) with:

  1. The supportsSetExpression capability. I found the necessary context in a previous GitHub Issue.
  2. The LoggingDebugSession class. This is the base class for the VS Code Mock Debug project's MockDebugSession class. That project appears to be how Debug Extension architecture is currently communicated. There is no discussion about what options exist for base classes here and no documentation about what LoggingDebugSession provides beyond its base class (yes logging, but via what mechanism exactly?). The only way to know is to look to the source code and learn it.

In general, I think the documentation for the DAP and VS Code's specific implementation thereof could be greatly enhanced by providing deeper context for features. As someone newly interfacing with the API and familiar with my own debugger's capabilities, it would make my life much easier to understand what end-user experience is enabled by a feature/capability; to understand the "why" behind an API, rather than just the "what".

Lenguaje dominante
HTML
Estrellas
1.8k
Forks
173
Merge medio
7 d 7 h
PR fusionados (30 d)
2

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de microsoft/debug-adapter-protocol

Todos los issues de microsoft/debug-adapter-protocol

Issues similares

Más issues de DevTools

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.