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

testing-rn.mdx (Under the Hood - Testing RN Changes)

Browse Source 
Summary: Restyle of page, including changes to spelling, grammar, links, and structure (where relevant).

Reviewed By: passy

Differential Revision: D36666807

fbshipit-source-id: 6da969a81a28fc7f9cd7cd8deb3fe341b5516ee2
This commit is contained in:
Kevin Strider
2022-05-26 03:44:28 -07:00
committed by Facebook GitHub Bot
parent e44cad5e99
commit 23f73f0b1e
1 changed files with 8 additions and 15 deletions
Download Patch File Download Diff File Expand all files Collapse all files

23
docs/extending/testing-rn.mdx
View File

@@ -5,22 +5,17 @@ sidebar_label: Testing RN Changes
--- ---
import useBaseUrl from '@docusaurus/useBaseUrl'; import useBaseUrl from '@docusaurus/useBaseUrl';
When making changes to the React Native integration, it can be helpful to When making changes to the React Native integration, it can be helpful to test them directly in the [ReactNativeFlipperExample](https://github.com/facebook/flipper/tree/main/react-native/ReactNativeFlipperExample) we provide in the repository. However, the app builds against a production release of Flipper and not the version checked in in the repository.
test them directly in the [sample
app](https://github.com/facebook/flipper/tree/main/react-native/ReactNativeFlipperExample)
we provide in the repository. However, the app is building against a production release
of Flipper and not the version checked in in the repository.
In order to test against the changes you have made, you need to publish a Flipper In order to test against the changes you have made, you need to publish a Flipper release locally.
release locally.
## Publishing a Local Release ## Publishing a Local Release
First, create a unique version number. This step is optional but is helpful First, create a unique version number. This step is optional but is helpful to prevent accidentally testing against the wrong version.
to prevent accidentally testing against the wrong version.
In the top-level `gradle.properties`, change the version: In the top-level `gradle.properties`, change the version:
```
```bash
... ...
# POM publishing constants # POM publishing constants
VERSION_NAME=0.44.99-SNAPSHOT # Change this one. VERSION_NAME=0.44.99-SNAPSHOT # Change this one.
@@ -28,16 +23,14 @@ GROUP=com.facebook.flipper
... ...
``` ```
Now, run `./gradlew installArchives -PRELEASE_SIGNING_ENABLED=false` in the root of the repository. This will Now, run `./gradlew installArchives -PRELEASE_SIGNING_ENABLED=false` in the root of the repository. This will place the artifact files in your local `~/.m2/repository` folder.
place the artifact files in your local `~/.m2/repository` folder.
## Using the new Release ## Using the new Release
Usually, you need to change your project to also pick up files in `mavenLocal()`. Usually, you need to change your project to also pick up files in `mavenLocal()`. As this is already done, you can directly change the `FLIPPER_VERSION` to the previously used identifier
As this is already done, you can directly change the `FLIPPER_VERSION` to the previously used identifier
in `react-native/ReactNativeFlipperExample/android/gradle.properties`: in `react-native/ReactNativeFlipperExample/android/gradle.properties`:
``` ```bash
# Version of flipper SDK to use with React Native # Version of flipper SDK to use with React Native
FLIPPER_VERSION=0.30.2 FLIPPER_VERSION=0.30.2
FLIPPER_VERSION=0.44.99-SNAPSHOT FLIPPER_VERSION=0.44.99-SNAPSHOT