Skip to content

Commit 3f587a4

Browse files
committed
Added VSCode section to README
1 parent f1c87af commit 3f587a4

File tree

2 files changed

+10
-0
lines changed

2 files changed

+10
-0
lines changed

README.md

+10
Original file line numberDiff line numberDiff line change
@@ -70,6 +70,16 @@ which will attempt to open your app in the iOS Simulator if you're on a Mac and
7070

7171
Some times, and especially when tweaking anything in the `package.json`, Babel configuration (`.babelrc`) or the Jest configuration (`jest.config.js`), your changes might seem to not take effect as expected. On those times, you might need to clean various caches before starting the packager. To do that, run the script: `yarn start:reset`. Other times, you might want to reinstall the NPM packages from scratch and the `yarn clean:install` script can be handy.
7272

73+
## Developing with Visual Studio Code
74+
75+
Although you're not required to use Visual Studio Code for developing gutenberg-mobile, it is the recommended IDE and we have some configuration for it.
76+
77+
When you first open the project in Visual Studio, you will be prompted to install some recommended extensions. This will help with some things like type checking and debugging.
78+
79+
![Prompt to install recommended extensions](images/recommended-extensions.png)
80+
81+
One of the extensions we are using is the [React Native Tools](https://marketplace.visualstudio.com/items?itemName=vsmobile.vscode-react-native). This allows you to run the packager from VSCode or launch the application on iOS or Android. It also adds some debug configurations so you can set breakpoints and debug the application directly from VSCode. Take a look at the [extension documentation](https://marketplace.visualstudio.com/items?itemName=vsmobile.vscode-react-native) for more details.
82+
7383
## Test
7484

7585
Use the following command to run the test suite:

images/recommended-extensions.png

13.3 KB
Loading

0 commit comments

Comments
 (0)