|
12 | 12 |
|
13 | 13 | > While it's possible to use [`npm`](https://github.com/npm/cli), the tooling is built around [`yarn`](https://classic.yarnpkg.com/), so you'll have an easier time if you use `yarn` for development. |
14 | 14 |
|
15 | | -While developing, you can run the [example app](/example/) to test your changes. Any changes you make in your library's JavaScript code will be reflected in the example app without a rebuild. If you change any native code, then you'll need to rebuild the example app. |
| 15 | +While developing, you can run the example apps to test your changes: |
| 16 | + |
| 17 | +- **[Standard Example](/examples/example/)** - Full React Native app (Runs on Old React Native Architecture) |
| 18 | +- **[Expo Example](/examples/expo-example/)** - Expo-based app (Runs on New React Native Architecture) |
| 19 | + |
| 20 | +Any changes you make in your library's JavaScript code will be reflected in the example apps without a rebuild. If you change any native code, then you'll need to rebuild the example apps. |
16 | 21 |
|
17 | 22 | To start the packager: |
18 | 23 |
|
@@ -51,9 +56,9 @@ Remember to add tests for your change if possible. Run the unit tests by: |
51 | 56 | yarn test |
52 | 57 | ``` |
53 | 58 |
|
54 | | -To edit the Objective-C files, open `example/ios/IntercomReactNativeExample.xcworkspace` in XCode and find the source files at `Pods > Development Pods > intercom-react-native`. |
| 59 | +To edit the Objective-C files, open `examples/example/ios/IntercomReactNativeExample.xcworkspace` in XCode and find the source files at `Pods > Development Pods > intercom-react-native`. |
55 | 60 |
|
56 | | -To edit the Kotlin files, open `example/android` in Android studio and find the source files at `intercomreactnative` under `Android`. |
| 61 | +To edit the Kotlin files, open `examples/example/android` in Android studio and find the source files at `intercomreactnative` under `Android`. |
57 | 62 |
|
58 | 63 | ### Commit message convention |
59 | 64 |
|
@@ -104,7 +109,7 @@ The `package.json` file contains various scripts for common tasks: |
104 | 109 |
|
105 | 110 | When you're sending a pull request: |
106 | 111 |
|
107 | | -### Make sure that Pull Request target is `dev` branch. |
| 112 | +### Make sure that Pull Request target is `dev` branch |
108 | 113 |
|
109 | 114 | - Prefer small pull requests focused on one change. |
110 | 115 | - Verify that linters and tests are passing. |
@@ -188,11 +193,11 @@ Community leaders will follow these Community Impact Guidelines in determining t |
188 | 193 | ### Attribution |
189 | 194 |
|
190 | 195 | This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 2.0, |
191 | | -available at https://www.contributor-covenant.org/version/2/0/code_of_conduct.html. |
| 196 | +available at [https://www.contributor-covenant.org/version/2/0/code_of_conduct.html](https://www.contributor-covenant.org/version/2/0/code_of_conduct.html). |
192 | 197 |
|
193 | 198 | Community Impact Guidelines were inspired by [Mozilla's code of conduct enforcement ladder](https://github.com/mozilla/diversity). |
194 | 199 |
|
195 | 200 | [homepage]: https://www.contributor-covenant.org |
196 | 201 |
|
197 | 202 | For answers to common questions about this code of conduct, see the FAQ at |
198 | | -https://www.contributor-covenant.org/faq. Translations are available at https://www.contributor-covenant.org/translations. |
| 203 | +[https://www.contributor-covenant.org/faq](https://www.contributor-covenant.org/faq). Translations are available at [https://www.contributor-covenant.org/translations](https://www.contributor-covenant.org/translations). |
0 commit comments