diff --git a/docs/the-new-architecture/native-modules-custom-events.md b/docs/the-new-architecture/native-modules-custom-events.md index c44bbf93c16..caab48f3b04 100644 --- a/docs/the-new-architecture/native-modules-custom-events.md +++ b/docs/the-new-architecture/native-modules-custom-events.md @@ -316,7 +316,7 @@ First, you need to import a couple of types that you need to use to create the e - `import com.facebook.react.bridge.Arguments` - `import com.facebook.react.bridge.WritableMap` -Secondly, you need to implement the logic that actually emits the event to JS. In case of complex types, like the `KeyValuePair` defined in the specs, Codegen will generate a function that expects a `ReadableMap` as a parameter. You can create the `ReadableMap` by using the `Arguments.createMap()` factory method, and use the `apply` function to populate the map. It's your responsibility to make sure that the the keys you are using in the map are the same properties that are defined in the spec type in JS. +Secondly, you need to implement the logic that actually emits the event to JS. In case of complex types, like the `KeyValuePair` defined in the specs, Codegen will generate a function that expects a `ReadableMap` as a parameter. You can create the `ReadableMap` by using the `Arguments.createMap()` factory method, and use the `apply` function to populate the map. It's your responsibility to make sure that the keys you are using in the map are the same properties that are defined in the spec type in JS. @@ -361,7 +361,7 @@ NS_ASSUME_NONNULL_END The `NativeLocalStorageSpecBase` is a base class that provides the `emitOnKeyAdded` method and its basic implementation and boilerplate. Thanks to this class, you don't have to handle all the conversion between Objective-C and JSI that is required to send the event to JS. -In case of complex types, like the `KeyValuePair` defined in the specs, Codegen will generate a generic dictionary that you can populate on the native side. It's your responsibility to make sure that the the keys you are using in the dictionary are the same properties that are defined in the spec type in JS. +In case of complex types, like the `KeyValuePair` defined in the specs, Codegen will generate a generic dictionary that you can populate on the native side. It's your responsibility to make sure that the keys you are using in the dictionary are the same properties that are defined in the spec type in JS. diff --git a/website/versioned_docs/version-0.79/the-new-architecture/fabric-component-native-commands.md b/website/versioned_docs/version-0.79/the-new-architecture/fabric-component-native-commands.md index ca87360ba3a..2878bf2780b 100644 --- a/website/versioned_docs/version-0.79/the-new-architecture/fabric-component-native-commands.md +++ b/website/versioned_docs/version-0.79/the-new-architecture/fabric-component-native-commands.md @@ -99,7 +99,7 @@ In TypeScript, the `React.ElementRef` is deprecated. The correct type to use is ## 2. Update the App code to use the new command -Now you can use the command in the the app. +Now you can use the command in the app. diff --git a/website/versioned_docs/version-0.79/the-new-architecture/native-modules-custom-events.md b/website/versioned_docs/version-0.79/the-new-architecture/native-modules-custom-events.md index e5394fa3d5c..c6a6c585c1d 100644 --- a/website/versioned_docs/version-0.79/the-new-architecture/native-modules-custom-events.md +++ b/website/versioned_docs/version-0.79/the-new-architecture/native-modules-custom-events.md @@ -319,7 +319,7 @@ First, you need to import a couple of types that you need to use to create the e - `import com.facebook.react.bridge.Arguments` - `import com.facebook.react.bridge.WritableMap` -Secondly, you need to implement the logic that actually emits the event to JS. In case of complex types, like the `KeyValuePair` defined in the specs, Codegen will generate a function that expects a `ReadableMap` as a parameter. You can create the `ReadableMap` by using the `Arguments.createMap()` factory method, and use the `apply` function to populate the map. It's your responsibility to make sure that the the keys you are using in the map are the same properties that are defined in the spec type in JS. +Secondly, you need to implement the logic that actually emits the event to JS. In case of complex types, like the `KeyValuePair` defined in the specs, Codegen will generate a function that expects a `ReadableMap` as a parameter. You can create the `ReadableMap` by using the `Arguments.createMap()` factory method, and use the `apply` function to populate the map. It's your responsibility to make sure that the keys you are using in the map are the same properties that are defined in the spec type in JS. @@ -364,7 +364,7 @@ NS_ASSUME_NONNULL_END The `NativeLocalStorageSpecBase` is a base class that provides the `emitOnKeyAdded` method and its basic implementation and boilerplate. Thanks to this class, you don't have to handle all the conversion between Objective-C and JSI that is required to send the event to JS. -In case of complex types, like the `KeyValuePair` defined in the specs, Codegen will generate a generic dictionary that you can populate on the native side. It's your responsibility to make sure that the the keys you are using in the dictionary are the same properties that are defined in the spec type in JS. +In case of complex types, like the `KeyValuePair` defined in the specs, Codegen will generate a generic dictionary that you can populate on the native side. It's your responsibility to make sure that the keys you are using in the dictionary are the same properties that are defined in the spec type in JS. diff --git a/website/versioned_docs/version-0.80/the-new-architecture/fabric-component-native-commands.md b/website/versioned_docs/version-0.80/the-new-architecture/fabric-component-native-commands.md index 5cb5dbd6710..44fa17d7d44 100644 --- a/website/versioned_docs/version-0.80/the-new-architecture/fabric-component-native-commands.md +++ b/website/versioned_docs/version-0.80/the-new-architecture/fabric-component-native-commands.md @@ -99,7 +99,7 @@ In TypeScript, the `React.ElementRef` is deprecated. The correct type to use is ## 2. Update the App code to use the new command -Now you can use the command in the the app. +Now you can use the command in the app. diff --git a/website/versioned_docs/version-0.80/the-new-architecture/native-modules-custom-events.md b/website/versioned_docs/version-0.80/the-new-architecture/native-modules-custom-events.md index c44bbf93c16..caab48f3b04 100644 --- a/website/versioned_docs/version-0.80/the-new-architecture/native-modules-custom-events.md +++ b/website/versioned_docs/version-0.80/the-new-architecture/native-modules-custom-events.md @@ -316,7 +316,7 @@ First, you need to import a couple of types that you need to use to create the e - `import com.facebook.react.bridge.Arguments` - `import com.facebook.react.bridge.WritableMap` -Secondly, you need to implement the logic that actually emits the event to JS. In case of complex types, like the `KeyValuePair` defined in the specs, Codegen will generate a function that expects a `ReadableMap` as a parameter. You can create the `ReadableMap` by using the `Arguments.createMap()` factory method, and use the `apply` function to populate the map. It's your responsibility to make sure that the the keys you are using in the map are the same properties that are defined in the spec type in JS. +Secondly, you need to implement the logic that actually emits the event to JS. In case of complex types, like the `KeyValuePair` defined in the specs, Codegen will generate a function that expects a `ReadableMap` as a parameter. You can create the `ReadableMap` by using the `Arguments.createMap()` factory method, and use the `apply` function to populate the map. It's your responsibility to make sure that the keys you are using in the map are the same properties that are defined in the spec type in JS. @@ -361,7 +361,7 @@ NS_ASSUME_NONNULL_END The `NativeLocalStorageSpecBase` is a base class that provides the `emitOnKeyAdded` method and its basic implementation and boilerplate. Thanks to this class, you don't have to handle all the conversion between Objective-C and JSI that is required to send the event to JS. -In case of complex types, like the `KeyValuePair` defined in the specs, Codegen will generate a generic dictionary that you can populate on the native side. It's your responsibility to make sure that the the keys you are using in the dictionary are the same properties that are defined in the spec type in JS. +In case of complex types, like the `KeyValuePair` defined in the specs, Codegen will generate a generic dictionary that you can populate on the native side. It's your responsibility to make sure that the keys you are using in the dictionary are the same properties that are defined in the spec type in JS. diff --git a/website/versioned_docs/version-0.81/the-new-architecture/fabric-component-native-commands.md b/website/versioned_docs/version-0.81/the-new-architecture/fabric-component-native-commands.md index 5cb5dbd6710..44fa17d7d44 100644 --- a/website/versioned_docs/version-0.81/the-new-architecture/fabric-component-native-commands.md +++ b/website/versioned_docs/version-0.81/the-new-architecture/fabric-component-native-commands.md @@ -99,7 +99,7 @@ In TypeScript, the `React.ElementRef` is deprecated. The correct type to use is ## 2. Update the App code to use the new command -Now you can use the command in the the app. +Now you can use the command in the app. diff --git a/website/versioned_docs/version-0.81/the-new-architecture/native-modules-custom-events.md b/website/versioned_docs/version-0.81/the-new-architecture/native-modules-custom-events.md index c44bbf93c16..caab48f3b04 100644 --- a/website/versioned_docs/version-0.81/the-new-architecture/native-modules-custom-events.md +++ b/website/versioned_docs/version-0.81/the-new-architecture/native-modules-custom-events.md @@ -316,7 +316,7 @@ First, you need to import a couple of types that you need to use to create the e - `import com.facebook.react.bridge.Arguments` - `import com.facebook.react.bridge.WritableMap` -Secondly, you need to implement the logic that actually emits the event to JS. In case of complex types, like the `KeyValuePair` defined in the specs, Codegen will generate a function that expects a `ReadableMap` as a parameter. You can create the `ReadableMap` by using the `Arguments.createMap()` factory method, and use the `apply` function to populate the map. It's your responsibility to make sure that the the keys you are using in the map are the same properties that are defined in the spec type in JS. +Secondly, you need to implement the logic that actually emits the event to JS. In case of complex types, like the `KeyValuePair` defined in the specs, Codegen will generate a function that expects a `ReadableMap` as a parameter. You can create the `ReadableMap` by using the `Arguments.createMap()` factory method, and use the `apply` function to populate the map. It's your responsibility to make sure that the keys you are using in the map are the same properties that are defined in the spec type in JS. @@ -361,7 +361,7 @@ NS_ASSUME_NONNULL_END The `NativeLocalStorageSpecBase` is a base class that provides the `emitOnKeyAdded` method and its basic implementation and boilerplate. Thanks to this class, you don't have to handle all the conversion between Objective-C and JSI that is required to send the event to JS. -In case of complex types, like the `KeyValuePair` defined in the specs, Codegen will generate a generic dictionary that you can populate on the native side. It's your responsibility to make sure that the the keys you are using in the dictionary are the same properties that are defined in the spec type in JS. +In case of complex types, like the `KeyValuePair` defined in the specs, Codegen will generate a generic dictionary that you can populate on the native side. It's your responsibility to make sure that the keys you are using in the dictionary are the same properties that are defined in the spec type in JS. diff --git a/website/versioned_docs/version-0.82/the-new-architecture/fabric-component-native-commands.md b/website/versioned_docs/version-0.82/the-new-architecture/fabric-component-native-commands.md index 5cb5dbd6710..44fa17d7d44 100644 --- a/website/versioned_docs/version-0.82/the-new-architecture/fabric-component-native-commands.md +++ b/website/versioned_docs/version-0.82/the-new-architecture/fabric-component-native-commands.md @@ -99,7 +99,7 @@ In TypeScript, the `React.ElementRef` is deprecated. The correct type to use is ## 2. Update the App code to use the new command -Now you can use the command in the the app. +Now you can use the command in the app. diff --git a/website/versioned_docs/version-0.82/the-new-architecture/native-modules-custom-events.md b/website/versioned_docs/version-0.82/the-new-architecture/native-modules-custom-events.md index c44bbf93c16..caab48f3b04 100644 --- a/website/versioned_docs/version-0.82/the-new-architecture/native-modules-custom-events.md +++ b/website/versioned_docs/version-0.82/the-new-architecture/native-modules-custom-events.md @@ -316,7 +316,7 @@ First, you need to import a couple of types that you need to use to create the e - `import com.facebook.react.bridge.Arguments` - `import com.facebook.react.bridge.WritableMap` -Secondly, you need to implement the logic that actually emits the event to JS. In case of complex types, like the `KeyValuePair` defined in the specs, Codegen will generate a function that expects a `ReadableMap` as a parameter. You can create the `ReadableMap` by using the `Arguments.createMap()` factory method, and use the `apply` function to populate the map. It's your responsibility to make sure that the the keys you are using in the map are the same properties that are defined in the spec type in JS. +Secondly, you need to implement the logic that actually emits the event to JS. In case of complex types, like the `KeyValuePair` defined in the specs, Codegen will generate a function that expects a `ReadableMap` as a parameter. You can create the `ReadableMap` by using the `Arguments.createMap()` factory method, and use the `apply` function to populate the map. It's your responsibility to make sure that the keys you are using in the map are the same properties that are defined in the spec type in JS. @@ -361,7 +361,7 @@ NS_ASSUME_NONNULL_END The `NativeLocalStorageSpecBase` is a base class that provides the `emitOnKeyAdded` method and its basic implementation and boilerplate. Thanks to this class, you don't have to handle all the conversion between Objective-C and JSI that is required to send the event to JS. -In case of complex types, like the `KeyValuePair` defined in the specs, Codegen will generate a generic dictionary that you can populate on the native side. It's your responsibility to make sure that the the keys you are using in the dictionary are the same properties that are defined in the spec type in JS. +In case of complex types, like the `KeyValuePair` defined in the specs, Codegen will generate a generic dictionary that you can populate on the native side. It's your responsibility to make sure that the keys you are using in the dictionary are the same properties that are defined in the spec type in JS. diff --git a/website/versioned_docs/version-0.83/the-new-architecture/fabric-component-native-commands.md b/website/versioned_docs/version-0.83/the-new-architecture/fabric-component-native-commands.md index 5cb5dbd6710..44fa17d7d44 100644 --- a/website/versioned_docs/version-0.83/the-new-architecture/fabric-component-native-commands.md +++ b/website/versioned_docs/version-0.83/the-new-architecture/fabric-component-native-commands.md @@ -99,7 +99,7 @@ In TypeScript, the `React.ElementRef` is deprecated. The correct type to use is ## 2. Update the App code to use the new command -Now you can use the command in the the app. +Now you can use the command in the app. diff --git a/website/versioned_docs/version-0.83/the-new-architecture/native-modules-custom-events.md b/website/versioned_docs/version-0.83/the-new-architecture/native-modules-custom-events.md index c44bbf93c16..caab48f3b04 100644 --- a/website/versioned_docs/version-0.83/the-new-architecture/native-modules-custom-events.md +++ b/website/versioned_docs/version-0.83/the-new-architecture/native-modules-custom-events.md @@ -316,7 +316,7 @@ First, you need to import a couple of types that you need to use to create the e - `import com.facebook.react.bridge.Arguments` - `import com.facebook.react.bridge.WritableMap` -Secondly, you need to implement the logic that actually emits the event to JS. In case of complex types, like the `KeyValuePair` defined in the specs, Codegen will generate a function that expects a `ReadableMap` as a parameter. You can create the `ReadableMap` by using the `Arguments.createMap()` factory method, and use the `apply` function to populate the map. It's your responsibility to make sure that the the keys you are using in the map are the same properties that are defined in the spec type in JS. +Secondly, you need to implement the logic that actually emits the event to JS. In case of complex types, like the `KeyValuePair` defined in the specs, Codegen will generate a function that expects a `ReadableMap` as a parameter. You can create the `ReadableMap` by using the `Arguments.createMap()` factory method, and use the `apply` function to populate the map. It's your responsibility to make sure that the keys you are using in the map are the same properties that are defined in the spec type in JS. @@ -361,7 +361,7 @@ NS_ASSUME_NONNULL_END The `NativeLocalStorageSpecBase` is a base class that provides the `emitOnKeyAdded` method and its basic implementation and boilerplate. Thanks to this class, you don't have to handle all the conversion between Objective-C and JSI that is required to send the event to JS. -In case of complex types, like the `KeyValuePair` defined in the specs, Codegen will generate a generic dictionary that you can populate on the native side. It's your responsibility to make sure that the the keys you are using in the dictionary are the same properties that are defined in the spec type in JS. +In case of complex types, like the `KeyValuePair` defined in the specs, Codegen will generate a generic dictionary that you can populate on the native side. It's your responsibility to make sure that the keys you are using in the dictionary are the same properties that are defined in the spec type in JS. diff --git a/website/versioned_docs/version-0.84/the-new-architecture/fabric-component-native-commands.md b/website/versioned_docs/version-0.84/the-new-architecture/fabric-component-native-commands.md index 5cb5dbd6710..44fa17d7d44 100644 --- a/website/versioned_docs/version-0.84/the-new-architecture/fabric-component-native-commands.md +++ b/website/versioned_docs/version-0.84/the-new-architecture/fabric-component-native-commands.md @@ -99,7 +99,7 @@ In TypeScript, the `React.ElementRef` is deprecated. The correct type to use is ## 2. Update the App code to use the new command -Now you can use the command in the the app. +Now you can use the command in the app. diff --git a/website/versioned_docs/version-0.84/the-new-architecture/native-modules-custom-events.md b/website/versioned_docs/version-0.84/the-new-architecture/native-modules-custom-events.md index c44bbf93c16..caab48f3b04 100644 --- a/website/versioned_docs/version-0.84/the-new-architecture/native-modules-custom-events.md +++ b/website/versioned_docs/version-0.84/the-new-architecture/native-modules-custom-events.md @@ -316,7 +316,7 @@ First, you need to import a couple of types that you need to use to create the e - `import com.facebook.react.bridge.Arguments` - `import com.facebook.react.bridge.WritableMap` -Secondly, you need to implement the logic that actually emits the event to JS. In case of complex types, like the `KeyValuePair` defined in the specs, Codegen will generate a function that expects a `ReadableMap` as a parameter. You can create the `ReadableMap` by using the `Arguments.createMap()` factory method, and use the `apply` function to populate the map. It's your responsibility to make sure that the the keys you are using in the map are the same properties that are defined in the spec type in JS. +Secondly, you need to implement the logic that actually emits the event to JS. In case of complex types, like the `KeyValuePair` defined in the specs, Codegen will generate a function that expects a `ReadableMap` as a parameter. You can create the `ReadableMap` by using the `Arguments.createMap()` factory method, and use the `apply` function to populate the map. It's your responsibility to make sure that the keys you are using in the map are the same properties that are defined in the spec type in JS. @@ -361,7 +361,7 @@ NS_ASSUME_NONNULL_END The `NativeLocalStorageSpecBase` is a base class that provides the `emitOnKeyAdded` method and its basic implementation and boilerplate. Thanks to this class, you don't have to handle all the conversion between Objective-C and JSI that is required to send the event to JS. -In case of complex types, like the `KeyValuePair` defined in the specs, Codegen will generate a generic dictionary that you can populate on the native side. It's your responsibility to make sure that the the keys you are using in the dictionary are the same properties that are defined in the spec type in JS. +In case of complex types, like the `KeyValuePair` defined in the specs, Codegen will generate a generic dictionary that you can populate on the native side. It's your responsibility to make sure that the keys you are using in the dictionary are the same properties that are defined in the spec type in JS. diff --git a/website/versioned_docs/version-0.85/the-new-architecture/fabric-component-native-commands.md b/website/versioned_docs/version-0.85/the-new-architecture/fabric-component-native-commands.md index 5cb5dbd6710..44fa17d7d44 100644 --- a/website/versioned_docs/version-0.85/the-new-architecture/fabric-component-native-commands.md +++ b/website/versioned_docs/version-0.85/the-new-architecture/fabric-component-native-commands.md @@ -99,7 +99,7 @@ In TypeScript, the `React.ElementRef` is deprecated. The correct type to use is ## 2. Update the App code to use the new command -Now you can use the command in the the app. +Now you can use the command in the app. diff --git a/website/versioned_docs/version-0.85/the-new-architecture/native-modules-custom-events.md b/website/versioned_docs/version-0.85/the-new-architecture/native-modules-custom-events.md index c44bbf93c16..caab48f3b04 100644 --- a/website/versioned_docs/version-0.85/the-new-architecture/native-modules-custom-events.md +++ b/website/versioned_docs/version-0.85/the-new-architecture/native-modules-custom-events.md @@ -316,7 +316,7 @@ First, you need to import a couple of types that you need to use to create the e - `import com.facebook.react.bridge.Arguments` - `import com.facebook.react.bridge.WritableMap` -Secondly, you need to implement the logic that actually emits the event to JS. In case of complex types, like the `KeyValuePair` defined in the specs, Codegen will generate a function that expects a `ReadableMap` as a parameter. You can create the `ReadableMap` by using the `Arguments.createMap()` factory method, and use the `apply` function to populate the map. It's your responsibility to make sure that the the keys you are using in the map are the same properties that are defined in the spec type in JS. +Secondly, you need to implement the logic that actually emits the event to JS. In case of complex types, like the `KeyValuePair` defined in the specs, Codegen will generate a function that expects a `ReadableMap` as a parameter. You can create the `ReadableMap` by using the `Arguments.createMap()` factory method, and use the `apply` function to populate the map. It's your responsibility to make sure that the keys you are using in the map are the same properties that are defined in the spec type in JS. @@ -361,7 +361,7 @@ NS_ASSUME_NONNULL_END The `NativeLocalStorageSpecBase` is a base class that provides the `emitOnKeyAdded` method and its basic implementation and boilerplate. Thanks to this class, you don't have to handle all the conversion between Objective-C and JSI that is required to send the event to JS. -In case of complex types, like the `KeyValuePair` defined in the specs, Codegen will generate a generic dictionary that you can populate on the native side. It's your responsibility to make sure that the the keys you are using in the dictionary are the same properties that are defined in the spec type in JS. +In case of complex types, like the `KeyValuePair` defined in the specs, Codegen will generate a generic dictionary that you can populate on the native side. It's your responsibility to make sure that the keys you are using in the dictionary are the same properties that are defined in the spec type in JS. diff --git a/website/versioned_docs/version-0.86/the-new-architecture/fabric-component-native-commands.md b/website/versioned_docs/version-0.86/the-new-architecture/fabric-component-native-commands.md index 5cb5dbd6710..44fa17d7d44 100644 --- a/website/versioned_docs/version-0.86/the-new-architecture/fabric-component-native-commands.md +++ b/website/versioned_docs/version-0.86/the-new-architecture/fabric-component-native-commands.md @@ -99,7 +99,7 @@ In TypeScript, the `React.ElementRef` is deprecated. The correct type to use is ## 2. Update the App code to use the new command -Now you can use the command in the the app. +Now you can use the command in the app. diff --git a/website/versioned_docs/version-0.86/the-new-architecture/native-modules-custom-events.md b/website/versioned_docs/version-0.86/the-new-architecture/native-modules-custom-events.md index c44bbf93c16..caab48f3b04 100644 --- a/website/versioned_docs/version-0.86/the-new-architecture/native-modules-custom-events.md +++ b/website/versioned_docs/version-0.86/the-new-architecture/native-modules-custom-events.md @@ -316,7 +316,7 @@ First, you need to import a couple of types that you need to use to create the e - `import com.facebook.react.bridge.Arguments` - `import com.facebook.react.bridge.WritableMap` -Secondly, you need to implement the logic that actually emits the event to JS. In case of complex types, like the `KeyValuePair` defined in the specs, Codegen will generate a function that expects a `ReadableMap` as a parameter. You can create the `ReadableMap` by using the `Arguments.createMap()` factory method, and use the `apply` function to populate the map. It's your responsibility to make sure that the the keys you are using in the map are the same properties that are defined in the spec type in JS. +Secondly, you need to implement the logic that actually emits the event to JS. In case of complex types, like the `KeyValuePair` defined in the specs, Codegen will generate a function that expects a `ReadableMap` as a parameter. You can create the `ReadableMap` by using the `Arguments.createMap()` factory method, and use the `apply` function to populate the map. It's your responsibility to make sure that the keys you are using in the map are the same properties that are defined in the spec type in JS. @@ -361,7 +361,7 @@ NS_ASSUME_NONNULL_END The `NativeLocalStorageSpecBase` is a base class that provides the `emitOnKeyAdded` method and its basic implementation and boilerplate. Thanks to this class, you don't have to handle all the conversion between Objective-C and JSI that is required to send the event to JS. -In case of complex types, like the `KeyValuePair` defined in the specs, Codegen will generate a generic dictionary that you can populate on the native side. It's your responsibility to make sure that the the keys you are using in the dictionary are the same properties that are defined in the spec type in JS. +In case of complex types, like the `KeyValuePair` defined in the specs, Codegen will generate a generic dictionary that you can populate on the native side. It's your responsibility to make sure that the keys you are using in the dictionary are the same properties that are defined in the spec type in JS. diff --git a/website/versioned_docs/version-0.87/the-new-architecture/native-modules-custom-events.md b/website/versioned_docs/version-0.87/the-new-architecture/native-modules-custom-events.md index c44bbf93c16..caab48f3b04 100644 --- a/website/versioned_docs/version-0.87/the-new-architecture/native-modules-custom-events.md +++ b/website/versioned_docs/version-0.87/the-new-architecture/native-modules-custom-events.md @@ -316,7 +316,7 @@ First, you need to import a couple of types that you need to use to create the e - `import com.facebook.react.bridge.Arguments` - `import com.facebook.react.bridge.WritableMap` -Secondly, you need to implement the logic that actually emits the event to JS. In case of complex types, like the `KeyValuePair` defined in the specs, Codegen will generate a function that expects a `ReadableMap` as a parameter. You can create the `ReadableMap` by using the `Arguments.createMap()` factory method, and use the `apply` function to populate the map. It's your responsibility to make sure that the the keys you are using in the map are the same properties that are defined in the spec type in JS. +Secondly, you need to implement the logic that actually emits the event to JS. In case of complex types, like the `KeyValuePair` defined in the specs, Codegen will generate a function that expects a `ReadableMap` as a parameter. You can create the `ReadableMap` by using the `Arguments.createMap()` factory method, and use the `apply` function to populate the map. It's your responsibility to make sure that the keys you are using in the map are the same properties that are defined in the spec type in JS. @@ -361,7 +361,7 @@ NS_ASSUME_NONNULL_END The `NativeLocalStorageSpecBase` is a base class that provides the `emitOnKeyAdded` method and its basic implementation and boilerplate. Thanks to this class, you don't have to handle all the conversion between Objective-C and JSI that is required to send the event to JS. -In case of complex types, like the `KeyValuePair` defined in the specs, Codegen will generate a generic dictionary that you can populate on the native side. It's your responsibility to make sure that the the keys you are using in the dictionary are the same properties that are defined in the spec type in JS. +In case of complex types, like the `KeyValuePair` defined in the specs, Codegen will generate a generic dictionary that you can populate on the native side. It's your responsibility to make sure that the keys you are using in the dictionary are the same properties that are defined in the spec type in JS. diff --git a/website/versioned_docs/version-0.88/the-new-architecture/native-modules-custom-events.md b/website/versioned_docs/version-0.88/the-new-architecture/native-modules-custom-events.md index c44bbf93c16..caab48f3b04 100644 --- a/website/versioned_docs/version-0.88/the-new-architecture/native-modules-custom-events.md +++ b/website/versioned_docs/version-0.88/the-new-architecture/native-modules-custom-events.md @@ -316,7 +316,7 @@ First, you need to import a couple of types that you need to use to create the e - `import com.facebook.react.bridge.Arguments` - `import com.facebook.react.bridge.WritableMap` -Secondly, you need to implement the logic that actually emits the event to JS. In case of complex types, like the `KeyValuePair` defined in the specs, Codegen will generate a function that expects a `ReadableMap` as a parameter. You can create the `ReadableMap` by using the `Arguments.createMap()` factory method, and use the `apply` function to populate the map. It's your responsibility to make sure that the the keys you are using in the map are the same properties that are defined in the spec type in JS. +Secondly, you need to implement the logic that actually emits the event to JS. In case of complex types, like the `KeyValuePair` defined in the specs, Codegen will generate a function that expects a `ReadableMap` as a parameter. You can create the `ReadableMap` by using the `Arguments.createMap()` factory method, and use the `apply` function to populate the map. It's your responsibility to make sure that the keys you are using in the map are the same properties that are defined in the spec type in JS. @@ -361,7 +361,7 @@ NS_ASSUME_NONNULL_END The `NativeLocalStorageSpecBase` is a base class that provides the `emitOnKeyAdded` method and its basic implementation and boilerplate. Thanks to this class, you don't have to handle all the conversion between Objective-C and JSI that is required to send the event to JS. -In case of complex types, like the `KeyValuePair` defined in the specs, Codegen will generate a generic dictionary that you can populate on the native side. It's your responsibility to make sure that the the keys you are using in the dictionary are the same properties that are defined in the spec type in JS. +In case of complex types, like the `KeyValuePair` defined in the specs, Codegen will generate a generic dictionary that you can populate on the native side. It's your responsibility to make sure that the keys you are using in the dictionary are the same properties that are defined in the spec type in JS.