Facebook/react-native
1
0
Fork 0
mirror of https://github.com/facebook/react-native.git synced 2025-11-01 09:14:26 +00:00
Code Issues Packages Projects Releases Wiki Activity

Update javadoc on BaseJavaModule (#41103)

Browse Source 
Summary:
Pull Request resolved: https://github.com/facebook/react-native/pull/41103

Update javadoc on BaseJavaModule to remove references to bridge classes

bypass-github-export-checks

changelog: [internal] internal

Reviewed By: luluwu2032

Differential Revision: D50294832

fbshipit-source-id: bca7be9e2e6a9ebee3e040b4b7e0d5c320627e26
This commit is contained in:
David Vacca
2023-10-23 20:02:38 -07:00
committed by Facebook GitHub Bot
parent 60297d50dc
commit d7d4989bdb
1 changed files with 9 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files
packages/react-native/ReactAndroid/src/main/java/com/facebook/react/bridge/BaseJavaModule.java
+9 -5
View File
@@ -92,7 +92,10 @@ public abstract class BaseJavaModule implements NativeModule {
onCatalystInstanceDestroy();
}
/** Subclasses can use this method to access catalyst context passed as a constructor. */
/**
* Subclasses can use this method to access {@link ReactApplicationContext} passed as a
* constructor.
*/
protected final ReactApplicationContext getReactApplicationContext() {
return Assertions.assertNotNull(
mReactApplicationContext,
@@ -100,10 +103,11 @@ public abstract class BaseJavaModule implements NativeModule {
}
/**
* Subclasses can use this method to access catalyst context passed as a constructor. Use this
* version to check that the underlying CatalystInstance is active before returning, and
* automatically have SoftExceptions or debug information logged for you. Consider using this
* whenever calling ReactApplicationContext methods that require the Catalyst instance be alive.
* Subclasses can use this method to access {@link ReactApplicationContext} passed as a
* constructor. Use this version to check that the underlying React Instance is active before
* returning, and automatically have SoftExceptions or debug information logged for you. Consider
* using this whenever calling ReactApplicationContext methods that require the React instance be
* alive.
*
* <p>This can return null at any time, but especially during teardown methods it's
* possible/likely.