From 8b696dea2704c0a76953e349628ce3da917d66f7 Mon Sep 17 00:00:00 2001 From: ksshp <141895476+ksshp@users.noreply.github.com> Date: Mon, 4 Dec 2023 15:33:33 +0800 Subject: [PATCH] Change 'use' to 'lose' to signify that functions are still accessible The statement at the end says that since the generated abstract class itself extends ReactContextBaseJavaModule, all the functions are still accessible. But the sentence reads "should not use", which does not make sense, and "should not lose" should instead be used. --- docs/new-architecture-library-android.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/new-architecture-library-android.md b/docs/new-architecture-library-android.md index c02ee40653d..688e200cf20 100644 --- a/docs/new-architecture-library-android.md +++ b/docs/new-architecture-library-android.md @@ -115,4 +115,4 @@ class NativeAwesomeManager(reactContext: ReactApplicationContext) : -Please note that the **generated abstract class** that you’re now extending (`MyAwesomeSpec` in this example) is itself extending `ReactContextBaseJavaModule`. Therefore you should not use access to any of the method/fields you were previously using (e.g., the `ReactApplicationContext` and so on). Moreover, the generated class will now also implement the `TurboModule` interface for you. +Please note that the **generated abstract class** that you’re now extending (`MyAwesomeSpec` in this example) is itself extending `ReactContextBaseJavaModule`. Therefore you should not lose access to any of the method/fields you were previously using (e.g., the `ReactApplicationContext` and so on). Moreover, the generated class will now also implement the `TurboModule` interface for you.