Skip to content
This repository was archived by the owner on May 20, 2025. It is now read-only.

Commit ab07913

Browse files
committed
Adding syntax identifiers
1 parent fcd8015 commit ab07913

File tree

1 file changed

+9
-9
lines changed

1 file changed

+9
-9
lines changed

README.md

Lines changed: 9 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -40,7 +40,7 @@ In order to ensure that your end users always have a functioning version of your
4040

4141
Once you've followed the general-purpose ["getting started"](http://codepush.tools/docs/getting-started.html) instructions for setting up your CodePush account, you can start CodePush-ifying your React Native app by running the following command from within your app's root directory:
4242

43-
```
43+
```shell
4444
npm install --save react-native-code-push
4545
```
4646

@@ -79,19 +79,19 @@ Once your Xcode project has been setup to build/link the CodePush plugin, you ne
7979

8080
1. Open up the `AppDelegate.m` file, and add an import statement for the CodePush headers:
8181

82-
```
82+
```objective-c
8383
#import "CodePush.h"
8484
```
8585

8686
2. Find the following line of code, which loads your JS Bundle from the app binary for production releases:
8787

88-
```
88+
```objective-c
8989
jsCodeLocation = [[NSBundle mainBundle] URLForResource:@"main" withExtension:@"jsbundle"];
9090
```
9191

9292
3. Replace it with this line:
9393

94-
```
94+
```objective-c
9595
jsCodeLocation = [CodePush bundleURL];
9696
```
9797

@@ -101,7 +101,7 @@ This change configures your app to always load the most recent version of your a
101101
102102
Typically, you're only going to want to use CodePush to resolve your JS bundle location within release builds, and therefore, we recommend using the `DEBUG` pre-processor macro to dynamically switch between using the packager server and CodePush, depending on whether you are debugging or not. This will make it much simpler to ensure you get the right behavior you want in production, while still being able to use the Chrome Dev Tools, live reload, etc. at debug-time.
103103

104-
```
104+
```objective-c
105105
NSURL *jsCodeLocation;
106106

107107
#ifdef DEBUG
@@ -207,13 +207,13 @@ The simplest way to do this is to perform the following in your app's root compo
207207
208208
1. Import the JavaScript module for CodePush:
209209
210-
```
210+
```javascript
211211
import CodePush from "react-native-code-push";
212212
```
213213
214214
2. Call the `sync` method from within the `componentDidMount` lifecycle event, to initiate a background update on each app start:
215215
216-
```
216+
```javascript
217217
CodePush.sync();
218218
```
219219
@@ -231,7 +231,7 @@ Once your app has been configured and distributed to your users, and you've made
231231
232232
Example Usage:
233233
234-
```
234+
```shell
235235
react-native bundle --platform ios --entry-file index.ios.js --bundle-output codepush.js --dev false
236236
code-push release MyApp codepush.js 1.0.2
237237
```
@@ -250,7 +250,7 @@ If you are using the new React Native [assets system](https://facebook.github.io
250250

251251
2. When calling `react-native bundle`, specify that your assets and JS bundle go into the directory you created in #1, and that you want a non-dev build for your respective platform and entry file. For example, assuming you called this directory "release", you could run the following command:
252252

253-
```
253+
```shell
254254
react-native bundle \
255255
--platform ios \
256256
--entry-file index.ios.js \

0 commit comments

Comments
 (0)