Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

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

Aperta
  • Qualcosa non va?
#450 1 commento 5 reazioni 0 assegnatari Vedi su GitHub

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
5/5
Tempo stimato
Più di una settimana
Idoneità per principianti
30/100
Tipo di issue
Documentazione
Chiarezza
Abbastanza chiara
Stato di attività
Ferma
Stack tecnologico
typescript, vscode
Ambito
developer-experience, documentation, tooling

Direzione di ricerca

Inizia con la Debugger Extension Guide, la DAP specification, la VS Code API Reference e VS Code Mock Debug, quindi esamina i file referenziati debugProtocol.ts e loggingDebugSession.ts. Confronta le loro descrizioni con le release notes di breakpointLocations e la discussione citata dell’issue. Il lavoro è completo quando viene aggiunto un contesto ufficiale che spieghi gli scopi delle funzionalità, il comportamento rivolto all’utente e le opzioni e il meccanismo di LoggingDebugSession.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

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".

Lingua principale
HTML
Stelle
1.8k
Fork
173
Merge medio
7g 7h
PR unite (30g)
2

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di microsoft/debug-adapter-protocol

Tutte le issue di microsoft/debug-adapter-protocol

Issue simili

Altre issue su DevTools

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.