From 2fe67162ae8abbe6fafbd070a5ff5762c7656254 Mon Sep 17 00:00:00 2001 From: Alper Cugun Date: Tue, 8 Mar 2016 07:06:42 -0800 Subject: [PATCH] Added objective-c class/module semantics Summary:This really stumped me and I thought it could be added to the docs. Closes https://github.com/facebook/react-native/pull/6136 Differential Revision: D2973912 Pulled By: mkonicek fb-gh-sync-id: 0da1a946e2c2ad00056037a6492be3e99096582e shipit-source-id: 0da1a946e2c2ad00056037a6492be3e99096582e --- docs/NativeModulesIOS.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/NativeModulesIOS.md b/docs/NativeModulesIOS.md index db20eda09ca..00c03ce5938 100644 --- a/docs/NativeModulesIOS.md +++ b/docs/NativeModulesIOS.md @@ -59,7 +59,7 @@ CalendarManager.addEvent('Birthday Party', '4 Privet Drive, Surrey'); > > The name of the method exported to JavaScript is the native method's name up to the first colon. React Native also defines a macro called `RCT_REMAP_METHOD()` to specify the JavaScript method's name. This is useful when multiple native methods are the same up to the first colon and would have conflicting JavaScript names. -The return type of bridge methods is always `void`. React Native bridge is asynchronous, so the only way to pass a result to JavaScript is by using callbacks or emitting events (see below). +The CalendarManager module is instantiated on the Objective-C side using a [CalendarManager new] call. The return type of bridge methods is always `void`. React Native bridge is asynchronous, so the only way to pass a result to JavaScript is by using callbacks or emitting events (see below). ## Argument Types