microsoft / microsoft/TypeScript

"Debugging Language Service in VS Code" documentation is weird

Offen
#19,254 10 Kommentare 0 Reaktionen 1 zugewiesene Person Auf GitHub ansehen

@DanielRosenwasser arbeitet bereits daran.

Seit 18.10.2017.

Docs
Vorherrschende Sprache
Go
Sterne
111k
Forks
14.3k
Ø Merge
1 T. 19 Std.
Gemergte PRs (30 T.)
117

Beschreibung

The "Debugging Language Service in VS Code" wiki is vague and sometimes confusing.

Update your user settings to use your development version of typescript, located in the .../TypeScript/built/local directory. The corresponding setting/path is

{
  "typescript.tsdk": "/path/to/repo/TypeScript/built/local"
}

User settings are stored per folder and it's not clear which folder should be used. Both typescript and vscode have been downloaded. There have been no instructions to open either version of code yet.

Debugging tsserver (server-side)
...
2. Update launch.json with an option to attach to the node instance, with sourcemaps from your built/local folder.

Again, which launch.json is being spoken about?

  1. Launch an instance of development vs code, and open a ts file.
  2. Launch an instance of stable vs code.
  3. Attach the stable vs code instance to the development instance.

Wouldn't it be easier to open an instance of code, change the launch.json and then open a .ts file or attach to the other instance?

It would be helpful to list the steps in order and with more detail, perhaps with an example path so that it's clear which instance of code is being opened, which folder said instance is opening (if any) and which files are being edited.

Given that there aren't too many steps, it should be quite reasonable to list all steps for each debugging excercise.

Beitragsleitfaden

Beitragsleitfaden öffnen

Erste Schritte

  1. Lies das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreib ins Issue, dass du es übernimmst — das erspart doppelte Arbeit.
  3. Forke das Repository und arbeite in einem Branch.
  4. Öffne einen Pull Request, der die Issue-Nummer nennt.

Bewertung

Dieses Issue wurde noch nicht bewertet.

Neue Issues direkt in Ihr Postfach

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