From cafba9412b71d2dd132f3b7f6ff19e1bf05070d5 Mon Sep 17 00:00:00 2001 From: Website Deployment Script Date: Sun, 22 Apr 2018 15:13:40 +0000 Subject: [PATCH] Deploy website Deploy website version based on c25448398257625da92f180ad2c203917935189f --- docs/0.10/native-modules-ios.html | 2 +- docs/0.11/native-modules-ios.html | 2 +- docs/0.12/native-modules-ios.html | 2 +- docs/0.13/native-modules-ios.html | 2 +- docs/0.14/native-modules-ios.html | 2 +- docs/0.15/native-modules-ios.html | 2 +- docs/0.16/native-modules-ios.html | 2 +- docs/0.17/native-modules-ios.html | 2 +- docs/0.18/native-modules-ios.html | 2 +- docs/0.19/native-modules-ios.html | 2 +- docs/0.20/native-modules-ios.html | 2 +- docs/0.21/native-modules-ios.html | 2 +- docs/0.22/native-modules-ios.html | 2 +- docs/0.23/native-modules-ios.html | 2 +- docs/0.24/native-modules-ios.html | 2 +- docs/0.25/native-modules-ios.html | 2 +- docs/0.26/native-modules-ios.html | 2 +- docs/0.27/native-modules-ios.html | 2 +- docs/0.28/native-modules-ios.html | 2 +- docs/0.29/native-modules-ios.html | 2 +- docs/0.30/native-modules-ios.html | 2 +- docs/0.31/native-modules-ios.html | 2 +- docs/0.32/native-modules-ios.html | 2 +- docs/0.33/native-modules-ios.html | 2 +- docs/0.34/native-modules-ios.html | 2 +- docs/0.35/native-modules-ios.html | 2 +- docs/0.36/native-modules-ios.html | 2 +- docs/0.37/native-modules-ios.html | 2 +- docs/0.38/native-modules-ios.html | 2 +- docs/0.39/native-modules-ios.html | 2 +- docs/0.40/native-modules-ios.html | 2 +- docs/0.41/native-modules-ios.html | 2 +- docs/0.42/native-modules-ios.html | 2 +- docs/0.43/native-modules-ios.html | 2 +- docs/0.44/native-modules-ios.html | 2 +- docs/0.45/native-modules-ios.html | 2 +- docs/0.46/native-modules-ios.html | 2 +- docs/0.47/native-modules-ios.html | 2 +- docs/0.48/native-modules-ios.html | 2 +- docs/0.49/native-modules-ios.html | 2 +- docs/0.5/native-modules-ios.html | 2 +- docs/0.50/native-modules-ios.html | 2 +- docs/0.51/native-modules-ios.html | 2 +- docs/0.52/native-modules-ios.html | 2 +- docs/0.53/native-modules-ios.html | 2 +- docs/0.54/native-modules-ios.html | 2 +- docs/0.6/native-modules-ios.html | 2 +- docs/0.7/native-modules-ios.html | 2 +- docs/0.8/native-modules-ios.html | 2 +- docs/0.9/native-modules-ios.html | 2 +- docs/native-modules-ios.html | 2 +- docs/next/native-modules-ios.html | 2 +- 52 files changed, 52 insertions(+), 52 deletions(-) diff --git a/docs/0.10/native-modules-ios.html b/docs/0.10/native-modules-ios.html index 17ed7e70d6c..af4864a3ac1 100644 --- a/docs/0.10/native-modules-ios.html +++ b/docs/0.10/native-modules-ios.html @@ -142,7 +142,7 @@ RCT_EXPORT_METHOD(addEvent:(NSString *)name d

Promises

Native modules can also fulfill a promise, which can simplify your code, especially when using ES2016's async/await syntax. When the last parameters of a bridged native method are an RCTPromiseResolveBlock and RCTPromiseRejectBlock, its corresponding JS method will return a JS Promise object.

Refactoring the above code to use a promise instead of callbacks looks like this:

-
RCT_REMAP_METHOD(findEvents,
+
RCT_REMAP_METHOD(findEvents
                  findEventsWithResolver:(RCTPromiseResolveBlock)resolve
                  rejecter:(RCTPromiseRejectBlock)reject)
 {
diff --git a/docs/0.11/native-modules-ios.html b/docs/0.11/native-modules-ios.html
index 8e1d416cab1..ada53e6cac1 100644
--- a/docs/0.11/native-modules-ios.html
+++ b/docs/0.11/native-modules-ios.html
@@ -142,7 +142,7 @@ RCT_EXPORT_METHOD(addEvent:(NSString *)name d
 
Promises

 
Native modules can also fulfill a promise, which can simplify your code, especially when using ES2016's async/await syntax. When the last parameters of a bridged native method are an RCTPromiseResolveBlock and RCTPromiseRejectBlock, its corresponding JS method will return a JS Promise object.

 
Refactoring the above code to use a promise instead of callbacks looks like this:

-
RCT_REMAP_METHOD(findEvents,
+
RCT_REMAP_METHOD(findEvents
                  findEventsWithResolver:(RCTPromiseResolveBlock)resolve
                  rejecter:(RCTPromiseRejectBlock)reject)
 {
diff --git a/docs/0.12/native-modules-ios.html b/docs/0.12/native-modules-ios.html
index 2e7a113afb8..41d09690adb 100644
--- a/docs/0.12/native-modules-ios.html
+++ b/docs/0.12/native-modules-ios.html
@@ -142,7 +142,7 @@ RCT_EXPORT_METHOD(addEvent:(NSString *)name d
 
Promises

 
Native modules can also fulfill a promise, which can simplify your code, especially when using ES2016's async/await syntax. When the last parameters of a bridged native method are an RCTPromiseResolveBlock and RCTPromiseRejectBlock, its corresponding JS method will return a JS Promise object.

 
Refactoring the above code to use a promise instead of callbacks looks like this:

-
RCT_REMAP_METHOD(findEvents,
+
RCT_REMAP_METHOD(findEvents
                  findEventsWithResolver:(RCTPromiseResolveBlock)resolve
                  rejecter:(RCTPromiseRejectBlock)reject)
 {
diff --git a/docs/0.13/native-modules-ios.html b/docs/0.13/native-modules-ios.html
index 855ea883070..8efccdde6af 100644
--- a/docs/0.13/native-modules-ios.html
+++ b/docs/0.13/native-modules-ios.html
@@ -142,7 +142,7 @@ RCT_EXPORT_METHOD(addEvent:(NSString *)name d
 
Promises

 
Native modules can also fulfill a promise, which can simplify your code, especially when using ES2016's async/await syntax. When the last parameters of a bridged native method are an RCTPromiseResolveBlock and RCTPromiseRejectBlock, its corresponding JS method will return a JS Promise object.

 
Refactoring the above code to use a promise instead of callbacks looks like this:

-
RCT_REMAP_METHOD(findEvents,
+
RCT_REMAP_METHOD(findEvents
                  findEventsWithResolver:(RCTPromiseResolveBlock)resolve
                  rejecter:(RCTPromiseRejectBlock)reject)
 {
diff --git a/docs/0.14/native-modules-ios.html b/docs/0.14/native-modules-ios.html
index 26417e1156f..d625eb4b492 100644
--- a/docs/0.14/native-modules-ios.html
+++ b/docs/0.14/native-modules-ios.html
@@ -142,7 +142,7 @@ RCT_EXPORT_METHOD(addEvent:(NSString *)name d
 
Promises

 
Native modules can also fulfill a promise, which can simplify your code, especially when using ES2016's async/await syntax. When the last parameters of a bridged native method are an RCTPromiseResolveBlock and RCTPromiseRejectBlock, its corresponding JS method will return a JS Promise object.

 
Refactoring the above code to use a promise instead of callbacks looks like this:

-
RCT_REMAP_METHOD(findEvents,
+
RCT_REMAP_METHOD(findEvents
                  findEventsWithResolver:(RCTPromiseResolveBlock)resolve
                  rejecter:(RCTPromiseRejectBlock)reject)
 {
diff --git a/docs/0.15/native-modules-ios.html b/docs/0.15/native-modules-ios.html
index a66c6636322..667f24d7e0d 100644
--- a/docs/0.15/native-modules-ios.html
+++ b/docs/0.15/native-modules-ios.html
@@ -142,7 +142,7 @@ RCT_EXPORT_METHOD(addEvent:(NSString *)name d
 
Promises

 
Native modules can also fulfill a promise, which can simplify your code, especially when using ES2016's async/await syntax. When the last parameters of a bridged native method are an RCTPromiseResolveBlock and RCTPromiseRejectBlock, its corresponding JS method will return a JS Promise object.

 
Refactoring the above code to use a promise instead of callbacks looks like this:

-
RCT_REMAP_METHOD(findEvents,
+
RCT_REMAP_METHOD(findEvents
                  findEventsWithResolver:(RCTPromiseResolveBlock)resolve
                  rejecter:(RCTPromiseRejectBlock)reject)
 {
diff --git a/docs/0.16/native-modules-ios.html b/docs/0.16/native-modules-ios.html
index 472dba8ca2b..3649e5fbfaa 100644
--- a/docs/0.16/native-modules-ios.html
+++ b/docs/0.16/native-modules-ios.html
@@ -142,7 +142,7 @@ RCT_EXPORT_METHOD(addEvent:(NSString *)name d
 
Promises

 
Native modules can also fulfill a promise, which can simplify your code, especially when using ES2016's async/await syntax. When the last parameters of a bridged native method are an RCTPromiseResolveBlock and RCTPromiseRejectBlock, its corresponding JS method will return a JS Promise object.

 
Refactoring the above code to use a promise instead of callbacks looks like this:

-
RCT_REMAP_METHOD(findEvents,
+
RCT_REMAP_METHOD(findEvents
                  findEventsWithResolver:(RCTPromiseResolveBlock)resolve
                  rejecter:(RCTPromiseRejectBlock)reject)
 {
diff --git a/docs/0.17/native-modules-ios.html b/docs/0.17/native-modules-ios.html
index bbae5c633bc..03b86be94db 100644
--- a/docs/0.17/native-modules-ios.html
+++ b/docs/0.17/native-modules-ios.html
@@ -142,7 +142,7 @@ RCT_EXPORT_METHOD(addEvent:(NSString *)name d
 
Promises

 
Native modules can also fulfill a promise, which can simplify your code, especially when using ES2016's async/await syntax. When the last parameters of a bridged native method are an RCTPromiseResolveBlock and RCTPromiseRejectBlock, its corresponding JS method will return a JS Promise object.

 
Refactoring the above code to use a promise instead of callbacks looks like this:

-
RCT_REMAP_METHOD(findEvents,
+
RCT_REMAP_METHOD(findEvents
                  findEventsWithResolver:(RCTPromiseResolveBlock)resolve
                  rejecter:(RCTPromiseRejectBlock)reject)
 {
diff --git a/docs/0.18/native-modules-ios.html b/docs/0.18/native-modules-ios.html
index b9b68f137f8..23f79051533 100644
--- a/docs/0.18/native-modules-ios.html
+++ b/docs/0.18/native-modules-ios.html
@@ -142,7 +142,7 @@ RCT_EXPORT_METHOD(addEvent:(NSString *)name d
 
Promises

 
Native modules can also fulfill a promise, which can simplify your code, especially when using ES2016's async/await syntax. When the last parameters of a bridged native method are an RCTPromiseResolveBlock and RCTPromiseRejectBlock, its corresponding JS method will return a JS Promise object.

 
Refactoring the above code to use a promise instead of callbacks looks like this:

-
RCT_REMAP_METHOD(findEvents,
+
RCT_REMAP_METHOD(findEvents
                  findEventsWithResolver:(RCTPromiseResolveBlock)resolve
                  rejecter:(RCTPromiseRejectBlock)reject)
 {
diff --git a/docs/0.19/native-modules-ios.html b/docs/0.19/native-modules-ios.html
index 8888e99ab17..4083e140dc2 100644
--- a/docs/0.19/native-modules-ios.html
+++ b/docs/0.19/native-modules-ios.html
@@ -142,7 +142,7 @@ RCT_EXPORT_METHOD(addEvent:(NSString *)name d
 
Promises

 
Native modules can also fulfill a promise, which can simplify your code, especially when using ES2016's async/await syntax. When the last parameters of a bridged native method are an RCTPromiseResolveBlock and RCTPromiseRejectBlock, its corresponding JS method will return a JS Promise object.

 
Refactoring the above code to use a promise instead of callbacks looks like this:

-
RCT_REMAP_METHOD(findEvents,
+
RCT_REMAP_METHOD(findEvents
                  findEventsWithResolver:(RCTPromiseResolveBlock)resolve
                  rejecter:(RCTPromiseRejectBlock)reject)
 {
diff --git a/docs/0.20/native-modules-ios.html b/docs/0.20/native-modules-ios.html
index 3c1cd8e27b8..680f53c619a 100644
--- a/docs/0.20/native-modules-ios.html
+++ b/docs/0.20/native-modules-ios.html
@@ -142,7 +142,7 @@ RCT_EXPORT_METHOD(addEvent:(NSString *)name d
 
Promises

 
Native modules can also fulfill a promise, which can simplify your code, especially when using ES2016's async/await syntax. When the last parameters of a bridged native method are an RCTPromiseResolveBlock and RCTPromiseRejectBlock, its corresponding JS method will return a JS Promise object.

 
Refactoring the above code to use a promise instead of callbacks looks like this:

-
RCT_REMAP_METHOD(findEvents,
+
RCT_REMAP_METHOD(findEvents
                  findEventsWithResolver:(RCTPromiseResolveBlock)resolve
                  rejecter:(RCTPromiseRejectBlock)reject)
 {
diff --git a/docs/0.21/native-modules-ios.html b/docs/0.21/native-modules-ios.html
index 0924256ad6f..99ec954276e 100644
--- a/docs/0.21/native-modules-ios.html
+++ b/docs/0.21/native-modules-ios.html
@@ -142,7 +142,7 @@ RCT_EXPORT_METHOD(addEvent:(NSString *)name d
 
Promises

 
Native modules can also fulfill a promise, which can simplify your code, especially when using ES2016's async/await syntax. When the last parameters of a bridged native method are an RCTPromiseResolveBlock and RCTPromiseRejectBlock, its corresponding JS method will return a JS Promise object.

 
Refactoring the above code to use a promise instead of callbacks looks like this:

-
RCT_REMAP_METHOD(findEvents,
+
RCT_REMAP_METHOD(findEvents
                  findEventsWithResolver:(RCTPromiseResolveBlock)resolve
                  rejecter:(RCTPromiseRejectBlock)reject)
 {
diff --git a/docs/0.22/native-modules-ios.html b/docs/0.22/native-modules-ios.html
index f67f02aa5bc..5a7aef1757d 100644
--- a/docs/0.22/native-modules-ios.html
+++ b/docs/0.22/native-modules-ios.html
@@ -142,7 +142,7 @@ RCT_EXPORT_METHOD(addEvent:(NSString *)name d
 
Promises

 
Native modules can also fulfill a promise, which can simplify your code, especially when using ES2016's async/await syntax. When the last parameters of a bridged native method are an RCTPromiseResolveBlock and RCTPromiseRejectBlock, its corresponding JS method will return a JS Promise object.

 
Refactoring the above code to use a promise instead of callbacks looks like this:

-
RCT_REMAP_METHOD(findEvents,
+
RCT_REMAP_METHOD(findEvents
                  findEventsWithResolver:(RCTPromiseResolveBlock)resolve
                  rejecter:(RCTPromiseRejectBlock)reject)
 {
diff --git a/docs/0.23/native-modules-ios.html b/docs/0.23/native-modules-ios.html
index 872ec097b07..daab55cf0c8 100644
--- a/docs/0.23/native-modules-ios.html
+++ b/docs/0.23/native-modules-ios.html
@@ -142,7 +142,7 @@ RCT_EXPORT_METHOD(addEvent:(NSString *)name d
 
Promises

 
Native modules can also fulfill a promise, which can simplify your code, especially when using ES2016's async/await syntax. When the last parameters of a bridged native method are an RCTPromiseResolveBlock and RCTPromiseRejectBlock, its corresponding JS method will return a JS Promise object.

 
Refactoring the above code to use a promise instead of callbacks looks like this:

-
RCT_REMAP_METHOD(findEvents,
+
RCT_REMAP_METHOD(findEvents
                  findEventsWithResolver:(RCTPromiseResolveBlock)resolve
                  rejecter:(RCTPromiseRejectBlock)reject)
 {
diff --git a/docs/0.24/native-modules-ios.html b/docs/0.24/native-modules-ios.html
index b18f80c34cd..311cf2b5079 100644
--- a/docs/0.24/native-modules-ios.html
+++ b/docs/0.24/native-modules-ios.html
@@ -142,7 +142,7 @@ RCT_EXPORT_METHOD(addEvent:(NSString *)name d
 
Promises

 
Native modules can also fulfill a promise, which can simplify your code, especially when using ES2016's async/await syntax. When the last parameters of a bridged native method are an RCTPromiseResolveBlock and RCTPromiseRejectBlock, its corresponding JS method will return a JS Promise object.

 
Refactoring the above code to use a promise instead of callbacks looks like this:

-
RCT_REMAP_METHOD(findEvents,
+
RCT_REMAP_METHOD(findEvents
                  findEventsWithResolver:(RCTPromiseResolveBlock)resolve
                  rejecter:(RCTPromiseRejectBlock)reject)
 {
diff --git a/docs/0.25/native-modules-ios.html b/docs/0.25/native-modules-ios.html
index 3e2b79624ae..1206185bfab 100644
--- a/docs/0.25/native-modules-ios.html
+++ b/docs/0.25/native-modules-ios.html
@@ -142,7 +142,7 @@ RCT_EXPORT_METHOD(addEvent:(NSString *)name d
 
Promises

 
Native modules can also fulfill a promise, which can simplify your code, especially when using ES2016's async/await syntax. When the last parameters of a bridged native method are an RCTPromiseResolveBlock and RCTPromiseRejectBlock, its corresponding JS method will return a JS Promise object.

 
Refactoring the above code to use a promise instead of callbacks looks like this:

-
RCT_REMAP_METHOD(findEvents,
+
RCT_REMAP_METHOD(findEvents
                  findEventsWithResolver:(RCTPromiseResolveBlock)resolve
                  rejecter:(RCTPromiseRejectBlock)reject)
 {
diff --git a/docs/0.26/native-modules-ios.html b/docs/0.26/native-modules-ios.html
index 7f700a60b90..5ee37e28c16 100644
--- a/docs/0.26/native-modules-ios.html
+++ b/docs/0.26/native-modules-ios.html
@@ -142,7 +142,7 @@ RCT_EXPORT_METHOD(addEvent:(NSString *)name d
 
Promises

 
Native modules can also fulfill a promise, which can simplify your code, especially when using ES2016's async/await syntax. When the last parameters of a bridged native method are an RCTPromiseResolveBlock and RCTPromiseRejectBlock, its corresponding JS method will return a JS Promise object.

 
Refactoring the above code to use a promise instead of callbacks looks like this:

-
RCT_REMAP_METHOD(findEvents,
+
RCT_REMAP_METHOD(findEvents
                  findEventsWithResolver:(RCTPromiseResolveBlock)resolve
                  rejecter:(RCTPromiseRejectBlock)reject)
 {
diff --git a/docs/0.27/native-modules-ios.html b/docs/0.27/native-modules-ios.html
index 6d918f293de..e436ca9287c 100644
--- a/docs/0.27/native-modules-ios.html
+++ b/docs/0.27/native-modules-ios.html
@@ -142,7 +142,7 @@ RCT_EXPORT_METHOD(addEvent:(NSString *)name d
 
Promises

 
Native modules can also fulfill a promise, which can simplify your code, especially when using ES2016's async/await syntax. When the last parameters of a bridged native method are an RCTPromiseResolveBlock and RCTPromiseRejectBlock, its corresponding JS method will return a JS Promise object.

 
Refactoring the above code to use a promise instead of callbacks looks like this:

-
RCT_REMAP_METHOD(findEvents,
+
RCT_REMAP_METHOD(findEvents
                  findEventsWithResolver:(RCTPromiseResolveBlock)resolve
                  rejecter:(RCTPromiseRejectBlock)reject)
 {
diff --git a/docs/0.28/native-modules-ios.html b/docs/0.28/native-modules-ios.html
index fdb3f2a0f1d..4737c5e37af 100644
--- a/docs/0.28/native-modules-ios.html
+++ b/docs/0.28/native-modules-ios.html
@@ -142,7 +142,7 @@ RCT_EXPORT_METHOD(addEvent:(NSString *)name d
 
Promises

 
Native modules can also fulfill a promise, which can simplify your code, especially when using ES2016's async/await syntax. When the last parameters of a bridged native method are an RCTPromiseResolveBlock and RCTPromiseRejectBlock, its corresponding JS method will return a JS Promise object.

 
Refactoring the above code to use a promise instead of callbacks looks like this:

-
RCT_REMAP_METHOD(findEvents,
+
RCT_REMAP_METHOD(findEvents
                  findEventsWithResolver:(RCTPromiseResolveBlock)resolve
                  rejecter:(RCTPromiseRejectBlock)reject)
 {
diff --git a/docs/0.29/native-modules-ios.html b/docs/0.29/native-modules-ios.html
index 0f4a09701be..dd0b61ce70b 100644
--- a/docs/0.29/native-modules-ios.html
+++ b/docs/0.29/native-modules-ios.html
@@ -142,7 +142,7 @@ RCT_EXPORT_METHOD(addEvent:(NSString *)name d
 
Promises

 
Native modules can also fulfill a promise, which can simplify your code, especially when using ES2016's async/await syntax. When the last parameters of a bridged native method are an RCTPromiseResolveBlock and RCTPromiseRejectBlock, its corresponding JS method will return a JS Promise object.

 
Refactoring the above code to use a promise instead of callbacks looks like this:

-
RCT_REMAP_METHOD(findEvents,
+
RCT_REMAP_METHOD(findEvents
                  findEventsWithResolver:(RCTPromiseResolveBlock)resolve
                  rejecter:(RCTPromiseRejectBlock)reject)
 {
diff --git a/docs/0.30/native-modules-ios.html b/docs/0.30/native-modules-ios.html
index 9b534f197aa..b9d77297d34 100644
--- a/docs/0.30/native-modules-ios.html
+++ b/docs/0.30/native-modules-ios.html
@@ -142,7 +142,7 @@ RCT_EXPORT_METHOD(addEvent:(NSString *)name d
 
Promises

 
Native modules can also fulfill a promise, which can simplify your code, especially when using ES2016's async/await syntax. When the last parameters of a bridged native method are an RCTPromiseResolveBlock and RCTPromiseRejectBlock, its corresponding JS method will return a JS Promise object.

 
Refactoring the above code to use a promise instead of callbacks looks like this:

-
RCT_REMAP_METHOD(findEvents,
+
RCT_REMAP_METHOD(findEvents
                  findEventsWithResolver:(RCTPromiseResolveBlock)resolve
                  rejecter:(RCTPromiseRejectBlock)reject)
 {
diff --git a/docs/0.31/native-modules-ios.html b/docs/0.31/native-modules-ios.html
index d9a2f437cbf..d2faefb77d2 100644
--- a/docs/0.31/native-modules-ios.html
+++ b/docs/0.31/native-modules-ios.html
@@ -142,7 +142,7 @@ RCT_EXPORT_METHOD(addEvent:(NSString *)name d
 
Promises

 
Native modules can also fulfill a promise, which can simplify your code, especially when using ES2016's async/await syntax. When the last parameters of a bridged native method are an RCTPromiseResolveBlock and RCTPromiseRejectBlock, its corresponding JS method will return a JS Promise object.

 
Refactoring the above code to use a promise instead of callbacks looks like this:

-
RCT_REMAP_METHOD(findEvents,
+
RCT_REMAP_METHOD(findEvents
                  findEventsWithResolver:(RCTPromiseResolveBlock)resolve
                  rejecter:(RCTPromiseRejectBlock)reject)
 {
diff --git a/docs/0.32/native-modules-ios.html b/docs/0.32/native-modules-ios.html
index 87d34e477b0..9ba06093c42 100644
--- a/docs/0.32/native-modules-ios.html
+++ b/docs/0.32/native-modules-ios.html
@@ -142,7 +142,7 @@ RCT_EXPORT_METHOD(addEvent:(NSString *)name d
 
Promises

 
Native modules can also fulfill a promise, which can simplify your code, especially when using ES2016's async/await syntax. When the last parameters of a bridged native method are an RCTPromiseResolveBlock and RCTPromiseRejectBlock, its corresponding JS method will return a JS Promise object.

 
Refactoring the above code to use a promise instead of callbacks looks like this:

-
RCT_REMAP_METHOD(findEvents,
+
RCT_REMAP_METHOD(findEvents
                  findEventsWithResolver:(RCTPromiseResolveBlock)resolve
                  rejecter:(RCTPromiseRejectBlock)reject)
 {
diff --git a/docs/0.33/native-modules-ios.html b/docs/0.33/native-modules-ios.html
index 4cf61e710e2..968dfe19b63 100644
--- a/docs/0.33/native-modules-ios.html
+++ b/docs/0.33/native-modules-ios.html
@@ -142,7 +142,7 @@ RCT_EXPORT_METHOD(addEvent:(NSString *)name d
 
Promises

 
Native modules can also fulfill a promise, which can simplify your code, especially when using ES2016's async/await syntax. When the last parameters of a bridged native method are an RCTPromiseResolveBlock and RCTPromiseRejectBlock, its corresponding JS method will return a JS Promise object.

 
Refactoring the above code to use a promise instead of callbacks looks like this:

-
RCT_REMAP_METHOD(findEvents,
+
RCT_REMAP_METHOD(findEvents
                  findEventsWithResolver:(RCTPromiseResolveBlock)resolve
                  rejecter:(RCTPromiseRejectBlock)reject)
 {
diff --git a/docs/0.34/native-modules-ios.html b/docs/0.34/native-modules-ios.html
index d53de6b4967..dde46a19daf 100644
--- a/docs/0.34/native-modules-ios.html
+++ b/docs/0.34/native-modules-ios.html
@@ -142,7 +142,7 @@ RCT_EXPORT_METHOD(addEvent:(NSString *)name d
 
Promises

 
Native modules can also fulfill a promise, which can simplify your code, especially when using ES2016's async/await syntax. When the last parameters of a bridged native method are an RCTPromiseResolveBlock and RCTPromiseRejectBlock, its corresponding JS method will return a JS Promise object.

 
Refactoring the above code to use a promise instead of callbacks looks like this:

-
RCT_REMAP_METHOD(findEvents,
+
RCT_REMAP_METHOD(findEvents
                  findEventsWithResolver:(RCTPromiseResolveBlock)resolve
                  rejecter:(RCTPromiseRejectBlock)reject)
 {
diff --git a/docs/0.35/native-modules-ios.html b/docs/0.35/native-modules-ios.html
index af84418f14a..2bda171a943 100644
--- a/docs/0.35/native-modules-ios.html
+++ b/docs/0.35/native-modules-ios.html
@@ -142,7 +142,7 @@ RCT_EXPORT_METHOD(addEvent:(NSString *)name d
 
Promises

 
Native modules can also fulfill a promise, which can simplify your code, especially when using ES2016's async/await syntax. When the last parameters of a bridged native method are an RCTPromiseResolveBlock and RCTPromiseRejectBlock, its corresponding JS method will return a JS Promise object.

 
Refactoring the above code to use a promise instead of callbacks looks like this:

-
RCT_REMAP_METHOD(findEvents,
+
RCT_REMAP_METHOD(findEvents
                  findEventsWithResolver:(RCTPromiseResolveBlock)resolve
                  rejecter:(RCTPromiseRejectBlock)reject)
 {
diff --git a/docs/0.36/native-modules-ios.html b/docs/0.36/native-modules-ios.html
index 2f206577606..44dff31b3e8 100644
--- a/docs/0.36/native-modules-ios.html
+++ b/docs/0.36/native-modules-ios.html
@@ -142,7 +142,7 @@ RCT_EXPORT_METHOD(addEvent:(NSString *)name d
 
Promises

 
Native modules can also fulfill a promise, which can simplify your code, especially when using ES2016's async/await syntax. When the last parameters of a bridged native method are an RCTPromiseResolveBlock and RCTPromiseRejectBlock, its corresponding JS method will return a JS Promise object.

 
Refactoring the above code to use a promise instead of callbacks looks like this:

-
RCT_REMAP_METHOD(findEvents,
+
RCT_REMAP_METHOD(findEvents
                  findEventsWithResolver:(RCTPromiseResolveBlock)resolve
                  rejecter:(RCTPromiseRejectBlock)reject)
 {
diff --git a/docs/0.37/native-modules-ios.html b/docs/0.37/native-modules-ios.html
index c0924740ad6..3b231eaa112 100644
--- a/docs/0.37/native-modules-ios.html
+++ b/docs/0.37/native-modules-ios.html
@@ -142,7 +142,7 @@ RCT_EXPORT_METHOD(addEvent:(NSString *)name d
 
Promises

 
Native modules can also fulfill a promise, which can simplify your code, especially when using ES2016's async/await syntax. When the last parameters of a bridged native method are an RCTPromiseResolveBlock and RCTPromiseRejectBlock, its corresponding JS method will return a JS Promise object.

 
Refactoring the above code to use a promise instead of callbacks looks like this:

-
RCT_REMAP_METHOD(findEvents,
+
RCT_REMAP_METHOD(findEvents
                  findEventsWithResolver:(RCTPromiseResolveBlock)resolve
                  rejecter:(RCTPromiseRejectBlock)reject)
 {
diff --git a/docs/0.38/native-modules-ios.html b/docs/0.38/native-modules-ios.html
index 0afc31ad9c4..01be82c5a58 100644
--- a/docs/0.38/native-modules-ios.html
+++ b/docs/0.38/native-modules-ios.html
@@ -142,7 +142,7 @@ RCT_EXPORT_METHOD(addEvent:(NSString *)name d
 
Promises

 
Native modules can also fulfill a promise, which can simplify your code, especially when using ES2016's async/await syntax. When the last parameters of a bridged native method are an RCTPromiseResolveBlock and RCTPromiseRejectBlock, its corresponding JS method will return a JS Promise object.

 
Refactoring the above code to use a promise instead of callbacks looks like this:

-
RCT_REMAP_METHOD(findEvents,
+
RCT_REMAP_METHOD(findEvents
                  findEventsWithResolver:(RCTPromiseResolveBlock)resolve
                  rejecter:(RCTPromiseRejectBlock)reject)
 {
diff --git a/docs/0.39/native-modules-ios.html b/docs/0.39/native-modules-ios.html
index 620922c0ae7..b67cf622eb6 100644
--- a/docs/0.39/native-modules-ios.html
+++ b/docs/0.39/native-modules-ios.html
@@ -142,7 +142,7 @@ RCT_EXPORT_METHOD(addEvent:(NSString *)name d
 
Promises

 
Native modules can also fulfill a promise, which can simplify your code, especially when using ES2016's async/await syntax. When the last parameters of a bridged native method are an RCTPromiseResolveBlock and RCTPromiseRejectBlock, its corresponding JS method will return a JS Promise object.

 
Refactoring the above code to use a promise instead of callbacks looks like this:

-
RCT_REMAP_METHOD(findEvents,
+
RCT_REMAP_METHOD(findEvents
                  findEventsWithResolver:(RCTPromiseResolveBlock)resolve
                  rejecter:(RCTPromiseRejectBlock)reject)
 {
diff --git a/docs/0.40/native-modules-ios.html b/docs/0.40/native-modules-ios.html
index b40988f6f7c..a57a5609836 100644
--- a/docs/0.40/native-modules-ios.html
+++ b/docs/0.40/native-modules-ios.html
@@ -142,7 +142,7 @@ RCT_EXPORT_METHOD(addEvent:(NSString *)name d
 
Promises

 
Native modules can also fulfill a promise, which can simplify your code, especially when using ES2016's async/await syntax. When the last parameters of a bridged native method are an RCTPromiseResolveBlock and RCTPromiseRejectBlock, its corresponding JS method will return a JS Promise object.

 
Refactoring the above code to use a promise instead of callbacks looks like this:

-
RCT_REMAP_METHOD(findEvents,
+
RCT_REMAP_METHOD(findEvents
                  findEventsWithResolver:(RCTPromiseResolveBlock)resolve
                  rejecter:(RCTPromiseRejectBlock)reject)
 {
diff --git a/docs/0.41/native-modules-ios.html b/docs/0.41/native-modules-ios.html
index f1c79ab3843..18062c1ff1f 100644
--- a/docs/0.41/native-modules-ios.html
+++ b/docs/0.41/native-modules-ios.html
@@ -142,7 +142,7 @@ RCT_EXPORT_METHOD(addEvent:(NSString *)name d
 
Promises

 
Native modules can also fulfill a promise, which can simplify your code, especially when using ES2016's async/await syntax. When the last parameters of a bridged native method are an RCTPromiseResolveBlock and RCTPromiseRejectBlock, its corresponding JS method will return a JS Promise object.

 
Refactoring the above code to use a promise instead of callbacks looks like this:

-
RCT_REMAP_METHOD(findEvents,
+
RCT_REMAP_METHOD(findEvents
                  findEventsWithResolver:(RCTPromiseResolveBlock)resolve
                  rejecter:(RCTPromiseRejectBlock)reject)
 {
diff --git a/docs/0.42/native-modules-ios.html b/docs/0.42/native-modules-ios.html
index 99858b7ca92..478589932dc 100644
--- a/docs/0.42/native-modules-ios.html
+++ b/docs/0.42/native-modules-ios.html
@@ -142,7 +142,7 @@ RCT_EXPORT_METHOD(addEvent:(NSString *)name d
 
Promises

 
Native modules can also fulfill a promise, which can simplify your code, especially when using ES2016's async/await syntax. When the last parameters of a bridged native method are an RCTPromiseResolveBlock and RCTPromiseRejectBlock, its corresponding JS method will return a JS Promise object.

 
Refactoring the above code to use a promise instead of callbacks looks like this:

-
RCT_REMAP_METHOD(findEvents,
+
RCT_REMAP_METHOD(findEvents
                  findEventsWithResolver:(RCTPromiseResolveBlock)resolve
                  rejecter:(RCTPromiseRejectBlock)reject)
 {
diff --git a/docs/0.43/native-modules-ios.html b/docs/0.43/native-modules-ios.html
index 525a3ad9528..39b02efdf23 100644
--- a/docs/0.43/native-modules-ios.html
+++ b/docs/0.43/native-modules-ios.html
@@ -142,7 +142,7 @@ RCT_EXPORT_METHOD(addEvent:(NSString *)name d
 
Promises

 
Native modules can also fulfill a promise, which can simplify your code, especially when using ES2016's async/await syntax. When the last parameters of a bridged native method are an RCTPromiseResolveBlock and RCTPromiseRejectBlock, its corresponding JS method will return a JS Promise object.

 
Refactoring the above code to use a promise instead of callbacks looks like this:

-
RCT_REMAP_METHOD(findEvents,
+
RCT_REMAP_METHOD(findEvents
                  findEventsWithResolver:(RCTPromiseResolveBlock)resolve
                  rejecter:(RCTPromiseRejectBlock)reject)
 {
diff --git a/docs/0.44/native-modules-ios.html b/docs/0.44/native-modules-ios.html
index 80a3c9ba4a4..eeee191b71d 100644
--- a/docs/0.44/native-modules-ios.html
+++ b/docs/0.44/native-modules-ios.html
@@ -142,7 +142,7 @@ RCT_EXPORT_METHOD(addEvent:(NSString *)name d
 
Promises

 
Native modules can also fulfill a promise, which can simplify your code, especially when using ES2016's async/await syntax. When the last parameters of a bridged native method are an RCTPromiseResolveBlock and RCTPromiseRejectBlock, its corresponding JS method will return a JS Promise object.

 
Refactoring the above code to use a promise instead of callbacks looks like this:

-
RCT_REMAP_METHOD(findEvents,
+
RCT_REMAP_METHOD(findEvents
                  findEventsWithResolver:(RCTPromiseResolveBlock)resolve
                  rejecter:(RCTPromiseRejectBlock)reject)
 {
diff --git a/docs/0.45/native-modules-ios.html b/docs/0.45/native-modules-ios.html
index 6bf4fe195dc..127effa637e 100644
--- a/docs/0.45/native-modules-ios.html
+++ b/docs/0.45/native-modules-ios.html
@@ -142,7 +142,7 @@ RCT_EXPORT_METHOD(addEvent:(NSString *)name d
 
Promises

 
Native modules can also fulfill a promise, which can simplify your code, especially when using ES2016's async/await syntax. When the last parameters of a bridged native method are an RCTPromiseResolveBlock and RCTPromiseRejectBlock, its corresponding JS method will return a JS Promise object.

 
Refactoring the above code to use a promise instead of callbacks looks like this:

-
RCT_REMAP_METHOD(findEvents,
+
RCT_REMAP_METHOD(findEvents
                  findEventsWithResolver:(RCTPromiseResolveBlock)resolve
                  rejecter:(RCTPromiseRejectBlock)reject)
 {
diff --git a/docs/0.46/native-modules-ios.html b/docs/0.46/native-modules-ios.html
index 2f1dde3a42c..e72ec28d7d0 100644
--- a/docs/0.46/native-modules-ios.html
+++ b/docs/0.46/native-modules-ios.html
@@ -142,7 +142,7 @@ RCT_EXPORT_METHOD(addEvent:(NSString *)name d
 
Promises

 
Native modules can also fulfill a promise, which can simplify your code, especially when using ES2016's async/await syntax. When the last parameters of a bridged native method are an RCTPromiseResolveBlock and RCTPromiseRejectBlock, its corresponding JS method will return a JS Promise object.

 
Refactoring the above code to use a promise instead of callbacks looks like this:

-
RCT_REMAP_METHOD(findEvents,
+
RCT_REMAP_METHOD(findEvents
                  findEventsWithResolver:(RCTPromiseResolveBlock)resolve
                  rejecter:(RCTPromiseRejectBlock)reject)
 {
diff --git a/docs/0.47/native-modules-ios.html b/docs/0.47/native-modules-ios.html
index ce2c864a779..e21be0b6edb 100644
--- a/docs/0.47/native-modules-ios.html
+++ b/docs/0.47/native-modules-ios.html
@@ -142,7 +142,7 @@ RCT_EXPORT_METHOD(addEvent:(NSString *)name d
 
Promises

 
Native modules can also fulfill a promise, which can simplify your code, especially when using ES2016's async/await syntax. When the last parameters of a bridged native method are an RCTPromiseResolveBlock and RCTPromiseRejectBlock, its corresponding JS method will return a JS Promise object.

 
Refactoring the above code to use a promise instead of callbacks looks like this:

-
RCT_REMAP_METHOD(findEvents,
+
RCT_REMAP_METHOD(findEvents
                  findEventsWithResolver:(RCTPromiseResolveBlock)resolve
                  rejecter:(RCTPromiseRejectBlock)reject)
 {
diff --git a/docs/0.48/native-modules-ios.html b/docs/0.48/native-modules-ios.html
index fb8dab6b938..d2551f0cfd1 100644
--- a/docs/0.48/native-modules-ios.html
+++ b/docs/0.48/native-modules-ios.html
@@ -142,7 +142,7 @@ RCT_EXPORT_METHOD(addEvent:(NSString *)name d
 
Promises

 
Native modules can also fulfill a promise, which can simplify your code, especially when using ES2016's async/await syntax. When the last parameters of a bridged native method are an RCTPromiseResolveBlock and RCTPromiseRejectBlock, its corresponding JS method will return a JS Promise object.

 
Refactoring the above code to use a promise instead of callbacks looks like this:

-
RCT_REMAP_METHOD(findEvents,
+
RCT_REMAP_METHOD(findEvents
                  findEventsWithResolver:(RCTPromiseResolveBlock)resolve
                  rejecter:(RCTPromiseRejectBlock)reject)
 {
diff --git a/docs/0.49/native-modules-ios.html b/docs/0.49/native-modules-ios.html
index 6b44461d2e4..3f88bc9747f 100644
--- a/docs/0.49/native-modules-ios.html
+++ b/docs/0.49/native-modules-ios.html
@@ -142,7 +142,7 @@ RCT_EXPORT_METHOD(addEvent:(NSString *)name d
 
Promises

 
Native modules can also fulfill a promise, which can simplify your code, especially when using ES2016's async/await syntax. When the last parameters of a bridged native method are an RCTPromiseResolveBlock and RCTPromiseRejectBlock, its corresponding JS method will return a JS Promise object.

 
Refactoring the above code to use a promise instead of callbacks looks like this:

-
RCT_REMAP_METHOD(findEvents,
+
RCT_REMAP_METHOD(findEvents
                  findEventsWithResolver:(RCTPromiseResolveBlock)resolve
                  rejecter:(RCTPromiseRejectBlock)reject)
 {
diff --git a/docs/0.5/native-modules-ios.html b/docs/0.5/native-modules-ios.html
index ef7701cf5f4..2c9672ab84a 100644
--- a/docs/0.5/native-modules-ios.html
+++ b/docs/0.5/native-modules-ios.html
@@ -142,7 +142,7 @@ RCT_EXPORT_METHOD(addEvent:(NSString *)name d
 
Promises

 
Native modules can also fulfill a promise, which can simplify your code, especially when using ES2016's async/await syntax. When the last parameters of a bridged native method are an RCTPromiseResolveBlock and RCTPromiseRejectBlock, its corresponding JS method will return a JS Promise object.

 
Refactoring the above code to use a promise instead of callbacks looks like this:

-
RCT_REMAP_METHOD(findEvents,
+
RCT_REMAP_METHOD(findEvents
                  findEventsWithResolver:(RCTPromiseResolveBlock)resolve
                  rejecter:(RCTPromiseRejectBlock)reject)
 {
diff --git a/docs/0.50/native-modules-ios.html b/docs/0.50/native-modules-ios.html
index 09fdf8fd617..d4640c5d2da 100644
--- a/docs/0.50/native-modules-ios.html
+++ b/docs/0.50/native-modules-ios.html
@@ -142,7 +142,7 @@ RCT_EXPORT_METHOD(addEvent:(NSString *)name d
 
Promises

 
Native modules can also fulfill a promise, which can simplify your code, especially when using ES2016's async/await syntax. When the last parameters of a bridged native method are an RCTPromiseResolveBlock and RCTPromiseRejectBlock, its corresponding JS method will return a JS Promise object.

 
Refactoring the above code to use a promise instead of callbacks looks like this:

-
RCT_REMAP_METHOD(findEvents,
+
RCT_REMAP_METHOD(findEvents
                  findEventsWithResolver:(RCTPromiseResolveBlock)resolve
                  rejecter:(RCTPromiseRejectBlock)reject)
 {
diff --git a/docs/0.51/native-modules-ios.html b/docs/0.51/native-modules-ios.html
index 51a6508dd1a..99421b4b493 100644
--- a/docs/0.51/native-modules-ios.html
+++ b/docs/0.51/native-modules-ios.html
@@ -142,7 +142,7 @@ RCT_EXPORT_METHOD(addEvent:(NSString *)name d
 
Promises

 
Native modules can also fulfill a promise, which can simplify your code, especially when using ES2016's async/await syntax. When the last parameters of a bridged native method are an RCTPromiseResolveBlock and RCTPromiseRejectBlock, its corresponding JS method will return a JS Promise object.

 
Refactoring the above code to use a promise instead of callbacks looks like this:

-
RCT_REMAP_METHOD(findEvents,
+
RCT_REMAP_METHOD(findEvents
                  findEventsWithResolver:(RCTPromiseResolveBlock)resolve
                  rejecter:(RCTPromiseRejectBlock)reject)
 {
diff --git a/docs/0.52/native-modules-ios.html b/docs/0.52/native-modules-ios.html
index e79508204e7..e54e77bb1ec 100644
--- a/docs/0.52/native-modules-ios.html
+++ b/docs/0.52/native-modules-ios.html
@@ -142,7 +142,7 @@ RCT_EXPORT_METHOD(addEvent:(NSString *)name d
 
Promises

 
Native modules can also fulfill a promise, which can simplify your code, especially when using ES2016's async/await syntax. When the last parameters of a bridged native method are an RCTPromiseResolveBlock and RCTPromiseRejectBlock, its corresponding JS method will return a JS Promise object.

 
Refactoring the above code to use a promise instead of callbacks looks like this:

-
RCT_REMAP_METHOD(findEvents,
+
RCT_REMAP_METHOD(findEvents
                  findEventsWithResolver:(RCTPromiseResolveBlock)resolve
                  rejecter:(RCTPromiseRejectBlock)reject)
 {
diff --git a/docs/0.53/native-modules-ios.html b/docs/0.53/native-modules-ios.html
index e1f67619a42..b6e350d4c8c 100644
--- a/docs/0.53/native-modules-ios.html
+++ b/docs/0.53/native-modules-ios.html
@@ -142,7 +142,7 @@ RCT_EXPORT_METHOD(addEvent:(NSString *)name d
 
Promises

 
Native modules can also fulfill a promise, which can simplify your code, especially when using ES2016's async/await syntax. When the last parameters of a bridged native method are an RCTPromiseResolveBlock and RCTPromiseRejectBlock, its corresponding JS method will return a JS Promise object.

 
Refactoring the above code to use a promise instead of callbacks looks like this:

-
RCT_REMAP_METHOD(findEvents,
+
RCT_REMAP_METHOD(findEvents
                  findEventsWithResolver:(RCTPromiseResolveBlock)resolve
                  rejecter:(RCTPromiseRejectBlock)reject)
 {
diff --git a/docs/0.54/native-modules-ios.html b/docs/0.54/native-modules-ios.html
index 0cbd0f97ee9..37c5e79c7de 100644
--- a/docs/0.54/native-modules-ios.html
+++ b/docs/0.54/native-modules-ios.html
@@ -142,7 +142,7 @@ RCT_EXPORT_METHOD(addEvent:(NSString *)name d
 
Promises

 
Native modules can also fulfill a promise, which can simplify your code, especially when using ES2016's async/await syntax. When the last parameters of a bridged native method are an RCTPromiseResolveBlock and RCTPromiseRejectBlock, its corresponding JS method will return a JS Promise object.

 
Refactoring the above code to use a promise instead of callbacks looks like this:

-
RCT_REMAP_METHOD(findEvents,
+
RCT_REMAP_METHOD(findEvents
                  findEventsWithResolver:(RCTPromiseResolveBlock)resolve
                  rejecter:(RCTPromiseRejectBlock)reject)
 {
diff --git a/docs/0.6/native-modules-ios.html b/docs/0.6/native-modules-ios.html
index ed37a0651ed..2773c3d5fed 100644
--- a/docs/0.6/native-modules-ios.html
+++ b/docs/0.6/native-modules-ios.html
@@ -142,7 +142,7 @@ RCT_EXPORT_METHOD(addEvent:(NSString *)name d
 
Promises

 
Native modules can also fulfill a promise, which can simplify your code, especially when using ES2016's async/await syntax. When the last parameters of a bridged native method are an RCTPromiseResolveBlock and RCTPromiseRejectBlock, its corresponding JS method will return a JS Promise object.

 
Refactoring the above code to use a promise instead of callbacks looks like this:

-
RCT_REMAP_METHOD(findEvents,
+
RCT_REMAP_METHOD(findEvents
                  findEventsWithResolver:(RCTPromiseResolveBlock)resolve
                  rejecter:(RCTPromiseRejectBlock)reject)
 {
diff --git a/docs/0.7/native-modules-ios.html b/docs/0.7/native-modules-ios.html
index a0910232ec7..7f363cce22d 100644
--- a/docs/0.7/native-modules-ios.html
+++ b/docs/0.7/native-modules-ios.html
@@ -142,7 +142,7 @@ RCT_EXPORT_METHOD(addEvent:(NSString *)name d
 
Promises

 
Native modules can also fulfill a promise, which can simplify your code, especially when using ES2016's async/await syntax. When the last parameters of a bridged native method are an RCTPromiseResolveBlock and RCTPromiseRejectBlock, its corresponding JS method will return a JS Promise object.

 
Refactoring the above code to use a promise instead of callbacks looks like this:

-
RCT_REMAP_METHOD(findEvents,
+
RCT_REMAP_METHOD(findEvents
                  findEventsWithResolver:(RCTPromiseResolveBlock)resolve
                  rejecter:(RCTPromiseRejectBlock)reject)
 {
diff --git a/docs/0.8/native-modules-ios.html b/docs/0.8/native-modules-ios.html
index d6a48f43f00..063e3f2e0e2 100644
--- a/docs/0.8/native-modules-ios.html
+++ b/docs/0.8/native-modules-ios.html
@@ -142,7 +142,7 @@ RCT_EXPORT_METHOD(addEvent:(NSString *)name d
 
Promises

 
Native modules can also fulfill a promise, which can simplify your code, especially when using ES2016's async/await syntax. When the last parameters of a bridged native method are an RCTPromiseResolveBlock and RCTPromiseRejectBlock, its corresponding JS method will return a JS Promise object.

 
Refactoring the above code to use a promise instead of callbacks looks like this:

-
RCT_REMAP_METHOD(findEvents,
+
RCT_REMAP_METHOD(findEvents
                  findEventsWithResolver:(RCTPromiseResolveBlock)resolve
                  rejecter:(RCTPromiseRejectBlock)reject)
 {
diff --git a/docs/0.9/native-modules-ios.html b/docs/0.9/native-modules-ios.html
index 34548ac8d5d..47426c4061d 100644
--- a/docs/0.9/native-modules-ios.html
+++ b/docs/0.9/native-modules-ios.html
@@ -142,7 +142,7 @@ RCT_EXPORT_METHOD(addEvent:(NSString *)name d
 
Promises

 
Native modules can also fulfill a promise, which can simplify your code, especially when using ES2016's async/await syntax. When the last parameters of a bridged native method are an RCTPromiseResolveBlock and RCTPromiseRejectBlock, its corresponding JS method will return a JS Promise object.

 
Refactoring the above code to use a promise instead of callbacks looks like this:

-
RCT_REMAP_METHOD(findEvents,
+
RCT_REMAP_METHOD(findEvents
                  findEventsWithResolver:(RCTPromiseResolveBlock)resolve
                  rejecter:(RCTPromiseRejectBlock)reject)
 {
diff --git a/docs/native-modules-ios.html b/docs/native-modules-ios.html
index 8f59b159fbd..b061c8cab08 100644
--- a/docs/native-modules-ios.html
+++ b/docs/native-modules-ios.html
@@ -142,7 +142,7 @@ RCT_EXPORT_METHOD(addEvent:(NSString *)name d
 
Promises

 
Native modules can also fulfill a promise, which can simplify your code, especially when using ES2016's async/await syntax. When the last parameters of a bridged native method are an RCTPromiseResolveBlock and RCTPromiseRejectBlock, its corresponding JS method will return a JS Promise object.

 
Refactoring the above code to use a promise instead of callbacks looks like this:

-
RCT_REMAP_METHOD(findEvents,
+
RCT_REMAP_METHOD(findEvents
                  findEventsWithResolver:(RCTPromiseResolveBlock)resolve
                  rejecter:(RCTPromiseRejectBlock)reject)
 {
diff --git a/docs/next/native-modules-ios.html b/docs/next/native-modules-ios.html
index 5ae6c230834..af793ff7ed7 100644
--- a/docs/next/native-modules-ios.html
+++ b/docs/next/native-modules-ios.html
@@ -144,7 +144,7 @@ RCT_EXPORT_METHOD(addEvent:(NSString *)name d
 
Promises

 
Native modules can also fulfill a promise, which can simplify your code, especially when using ES2016's async/await syntax. When the last parameters of a bridged native method are an RCTPromiseResolveBlock and RCTPromiseRejectBlock, its corresponding JS method will return a JS Promise object.

 
Refactoring the above code to use a promise instead of callbacks looks like this:

-
RCT_REMAP_METHOD(findEvents,
+
RCT_REMAP_METHOD(findEvents
                  findEventsWithResolver:(RCTPromiseResolveBlock)resolve
                  rejecter:(RCTPromiseRejectBlock)reject)
 {