From 3706ea05b3f19d2227bc4560d00f2f72ae6337b6 Mon Sep 17 00:00:00 2001 From: Anton Nikolaev Date: Wed, 29 Jan 2020 04:07:27 -0800 Subject: [PATCH] Another small clarification for VSCode debugging instructions Summary: A small clarification after the question https://github.com/facebook/flipper/commit/7964772f82cc182bbe45be855150d227eceed796#comments Reviewed By: jknoxville Differential Revision: D19619402 fbshipit-source-id: c392c492fe5e9cd46d46c93f617288ac0a4d02a5 --- docs/extending/debugging.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/extending/debugging.md b/docs/extending/debugging.md index 843c678ad..0c58e45eb 100644 --- a/docs/extending/debugging.md +++ b/docs/extending/debugging.md @@ -21,7 +21,7 @@ To attach the running Flipper instance open new tab in Google Chrome, navigate t ## 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)