jens/flipper
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Another small clarification for VSCode debugging instructions

Browse Source 
Summary: A small clarification after the question 7964772f82 (comments)

Reviewed By: jknoxville

Differential Revision: D19619402

fbshipit-source-id: c392c492fe5e9cd46d46c93f617288ac0a4d02a5
This commit is contained in:
Anton Nikolaev
2020-01-29 04:07:27 -08:00
committed by Facebook Github Bot
parent 9699691eb6
commit 3706ea05b3
1 changed files with 1 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
docs/extending/debugging.md
View File

@@ -21,7 +21,7 @@ To attach the running Flipper instance open new tab in Google Chrome, navigate t
## Visual Studio Code ## Visual Studio Code
If you prefer to use the same editor for both coding and debugging, you can attach to the running Flipper instance for debugging right from Visual Studio Code. First of all, you need to install extension "Debugger for Chrome". Then, to start debugging, launch Flipper in development mode (`yarn start`), select `Debug and Run` tab in VSCode, and run task `Attach to Running Renderer`. By default this task is set as the first one, so you can just press `F5` to run it. If you prefer to use the same editor for both coding and debugging, you can attach to the running Flipper instance for debugging right from Visual Studio Code. First of all, you need to install extension "Debugger for Chrome". Then, to start debugging, open the root folder of Flipper repository in VSCode, execute `yarn start` in terminal to launch Flipper in development mode, select tab `Debug and Run`, and run task `Attach to Running Renderer`. By default this task is set as the first one, so you can just press `F5` to run it.
![Attach From Visual Studio Code](/docs/assets/debugging-from-vscode.png) ![Attach From Visual Studio Code](/docs/assets/debugging-from-vscode.png)