You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/legacy/native-modules-intro.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -17,9 +17,9 @@ There are different ways to write a native module for your React Native applicat
17
17
18
18
1. Creating a local library that can be imported in your React Native application. Read [Creating local libraries](local-library-setup) guide to learn more.
19
19
2. Directly within your React Native application's iOS/Android projects
20
-
3. As a NPM package that can be installed as a dependency by your/other React Native applications.
20
+
3. As an NPM package that can be installed as a dependency by your/other React Native applications.
21
21
22
-
This guide will first walk you through implementing a native module directly within a React Native application. However the native module you build in the following guide can be distributed as an NPM package. Check out the [Setting Up a Native Module as a NPM Package](native-modules-setup) guide if you are interested in doing so.
22
+
This guide will first walk you through implementing a native module directly within a React Native application. However the native module you build in the following guide can be distributed as an NPM package. Check out the [Setting Up a Native Module as an NPM Package](native-modules-setup) guide if you are interested in doing so.
If the value is greater than `0`, the fading edges will be set accordingly to the current scroll direction and position, indicating if there is more content to show.
Copy file name to clipboardExpand all lines: docs/the-new-architecture/create-module-library.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -93,7 +93,7 @@ That's it! You have moved all the required code out of your app and in a separat
93
93
94
94
## Testing your Library
95
95
96
-
The `create-react-native-library` comes with an useful example application that is already configured to work properly with the library. This is a great way to test it!
96
+
The `create-react-native-library` comes with a useful example application that is already configured to work properly with the library. This is a great way to test it!
97
97
98
98
If you look at the `example` folder, you can find the same structure of a new React Native application that you can create from the [`react-native-community/template`](https://github.com/react-native-community/template).
Copy file name to clipboardExpand all lines: docs/the-new-architecture/using-codegen.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -86,7 +86,7 @@ The rest of this guide assumes that you have a Native Turbo Module, a Native Fab
86
86
87
87
### Android
88
88
89
-
**Codegen** for Android is integrated with the React Native Gradle Plugin (RNGP). The RNGP contains a task that can be invoked that reads the configurations defined in the `package.json` file and execute **Codegen**. To run the gradle task, first navigate inside the `android`folder of your project. Then run:
89
+
**Codegen** for Android is integrated with the React Native Gradle Plugin (RNGP). The RNGP contains a task that can be invoked that reads the configurations defined in the `package.json` file and execute **Codegen**. To run the gradle task, first navigate inside the `android`folder of your project. Then run:
90
90
91
91
```bash
92
92
./gradlew generateCodegenArtifactsFromSchema
@@ -150,7 +150,7 @@ In the folder whose name was set up in the `codegenConfig.android.javaPackageNam
150
150
In the `jni` folder, finally, there is all the boilerplate code to connect JS to Android.
151
151
152
152
-`<codegenConfig.name>.h` this contains the interface of your custom C++ Turbo Native Modules.
153
-
-`<codegenConfig.name>-generated.cpp` this contains the glue code of your custom custom C++ Turbo Native Modules.
153
+
-`<codegenConfig.name>-generated.cpp` this contains the glue code of your custom C++ Turbo Native Modules.
154
154
-`react/renderer/components/<codegenConfig.name>`: this folder contains all the glue-code required by your custom component.
155
155
156
156
This structure has been generated by using the value `all` for the `codegenConfig.type` field. If you use the value `modules`, expect to see no `react/renderer/components/` folder. If you use the value `components`, expect not to see any of the other files.
@@ -232,7 +232,7 @@ Part of these generated files are used by React Native in the Core. Then there i
232
232
-`<codegenConfig.name>/<codegenConfig.name>.h`: this contains the interface of your custom iOS Turbo Native Modules.
233
233
-`<codegenConfig.name>/<codegenConfig.name>-generated.mm`: this contains the glue code of your custom iOS Turbo Native Modules.
234
234
-`<codegenConfig.name>JSI.h`: this contains the interface of your custom C++ Turbo Native Modules.
235
-
-`<codegenConfig.name>JSI-generated.h`: this contains the glue code of your custom custom C++ Turbo Native Modules.
235
+
-`<codegenConfig.name>JSI-generated.h`: this contains the glue code of your custom C++ Turbo Native Modules.
236
236
-`react/renderer/components/<codegenConfig.name>`: this folder contains all the glue-code required by your custom component.
237
237
238
238
This structure has been generated by using the value `all` for the `codegenConfig.type` field. If you use the value `modules`, expect to see no `react/renderer/components/` folder. If you use the value `components`, expect not to see any of the other files.
Copy file name to clipboardExpand all lines: docs/upgrading.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -19,7 +19,7 @@ Because typical React Native projects are essentially made up of an Android proj
19
19
20
20
You first need to select from and to which version you wish to upgrade, by default the latest major versions are selected. After selecting you can click the button "Show me how to upgrade".
21
21
22
-
💡 Major updates will show an "useful content" section on the top with links to help you out when upgrading.
22
+
💡 Major updates will show a "useful content" section on the top with links to help you out when upgrading.
Copy file name to clipboardExpand all lines: website/blog/2018-11-01-oss-roadmap.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -61,4 +61,4 @@ React Native is one of the [top open source projects on GitHub](https://octovers
61
61
62
62
## Timeline
63
63
64
-
We're planning to land these projects throughout the next year or so. Some of these efforts are already ongoing, such as [JSI which has already landed in open source](https://github.com/facebook/react-native/compare/e337bcafb0b017311c37f2dbc24e5a757af0a205...8427f64e06456f171f9df0316c6ca40613de7a20). Others will take a bit longer to complete, such as reducing the surface area. We'll do our best to keep the community up to date with our progress. Please join us in the [Discussions and Proposals](https://github.com/react-native-community/discussions-and-proposals) repository, a initiative from the React Native community that has led to the creation of several of the initiatives discussed in this roadmap.
64
+
We're planning to land these projects throughout the next year or so. Some of these efforts are already ongoing, such as [JSI which has already landed in open source](https://github.com/facebook/react-native/compare/e337bcafb0b017311c37f2dbc24e5a757af0a205...8427f64e06456f171f9df0316c6ca40613de7a20). Others will take a bit longer to complete, such as reducing the surface area. We'll do our best to keep the community up to date with our progress. Please join us in the [Discussions and Proposals](https://github.com/react-native-community/discussions-and-proposals) repository, an initiative from the React Native community that has led to the creation of several of the initiatives discussed in this roadmap.
If you want to add custom props to your native component, you can use `nativeConfig.props` on the web view.
348
348
349
-
For events, the event handler must always be set to a function. This means it isn't safe to use the event handler directly from `this.props`, as the user might not have provided one. The standard approach is to create a event handler in your class, and then invoking the event handler given in `this.props` if it exists.
349
+
For events, the event handler must always be set to a function. This means it isn't safe to use the event handler directly from `this.props`, as the user might not have provided one. The standard approach is to create an event handler in your class, and then invoking the event handler given in `this.props` if it exists.
350
350
351
351
If you are unsure how something should be implemented from the JS side, look at [WebView.android.js](https://github.com/react-native-webview/react-native-webview/blob/master/src/WebView.android.tsx) in the React Native WebView source.
If you want to add custom props to your native component, you can use `nativeConfig.props` on the web view. For iOS, you should also set the `nativeConfig.viewManager` prop with your custom WebView ViewManager as in the example above.
180
180
181
-
For events, the event handler must always be set to a function. This means it isn't safe to use the event handler directly from `this.props`, as the user might not have provided one. The standard approach is to create a event handler in your class, and then invoking the event handler given in `this.props` if it exists.
181
+
For events, the event handler must always be set to a function. This means it isn't safe to use the event handler directly from `this.props`, as the user might not have provided one. The standard approach is to create an event handler in your class, and then invoking the event handler given in `this.props` if it exists.
182
182
183
183
If you are unsure how something should be implemented from the JS side, look at [WebView.ios.tsx](https://github.com/react-native-webview/react-native-webview/blob/master/src/WebView.ios.tsx) in the React Native source.
Copy file name to clipboardExpand all lines: website/versioned_docs/version-0.70/native-modules-intro.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -16,9 +16,9 @@ The NativeModule system exposes instances of Java/Objective-C/C++ (native) class
16
16
There are two ways to write a native module for your React Native application:
17
17
18
18
1. Directly within your React Native application’s iOS/Android projects
19
-
2. As a NPM package that can be installed as a dependency by your/other React Native applications
19
+
2. As an NPM package that can be installed as a dependency by your/other React Native applications
20
20
21
-
This guide will first walk you through implementing a native module directly within a React Native application. However the native module you build in the following guide can be distributed as an NPM package. Check out the [Setting Up a Native Module as a NPM Package](native-modules-setup) guide if you are interested in doing so.
21
+
This guide will first walk you through implementing a native module directly within a React Native application. However the native module you build in the following guide can be distributed as an NPM package. Check out the [Setting Up a Native Module as an NPM Package](native-modules-setup) guide if you are interested in doing so.
0 commit comments