Added JS wrappers for ImageStore and ImageEditor

Summary:
public
Added JS wrappers for ImageStore(Manager) and ImageEditor(Manager) so they can be required in the normal way instead of accessed directly via NativeModules.

Reviewed By: dmmiller

Differential Revision: D2773822

fb-gh-sync-id: 6eeafd3f80a87b1b91a04a2aebad6e2fd31b0e98

Libraries/Image/ImageStore.js

@@ -0,0 +1,83 @@
+/**
+ * Copyright (c) 2015-present, Facebook, Inc.
+ * All rights reserved.
+ *
+ * This source code is licensed under the BSD-style license found in the
+ * LICENSE file in the root directory of this source tree. An additional grant
+ * of patent rights can be found in the PATENTS file in the same directory.
+ *
+ * @providesModule ImageStore
+ * @flow
+ */
+'use strict';
+
+const RCTImageStoreManager = require('NativeModules').ImageStoreManager;
+
+class ImageStore {
+  /**
+   * Check if the ImageStore contains image data for the specified URI.
+   * @platform ios
+   */
+  static hasImageForTag(uri: string, callback: (hasImage: bool) => void) {
+    if (RCTImageStoreManager.hasImageForTag) {
+      RCTImageStoreManager.hasImageForTag(uri, callback);
+    } else {
+      console.warn('hasImageForTag() not implemented');
+    }
+  }
+
+  /**
+   * Delete an image from the ImageStore. Images are stored in memory and
+   * must be manually removed when you are finished with them, otherwise they
+   * will continue to use up RAM until the app is terminated. It is safe to
+   * call `removeImageForTag()` without first calling `hasImageForTag()`, it
+   * will simply fail silently.
+   * @platform ios
+   */
+  static removeImageForTag(uri: string) {
+    if (RCTImageStoreManager.removeImageForTag) {
+      RCTImageStoreManager.removeImageForTag(uri);
+    } else {
+      console.warn('removeImageForTag() not implemented');
+    }
+  }
+
+  /**
+   * Stores a base64-encoded image in the ImageStore, and returns a URI that
+   * can be used to access or display the image later. Images are stored in
+   * memory only, and must be manually deleted when you are finished with
+   * them by calling `removeImageForTag()`.
+   *
+   * Note that it is very inefficient to transfer large quantities of binary
+   * data between JS and native code, so you should avoid calling this more
+   * than necessary.
+   */
+  static addImageFromBase64(
+    base64ImageData: string,
+    success: (uri: string) => void,
+    failure: (error: any) => void
+  ) {
+    RCTImageStoreManager.addImageFromBase64(base64ImageData, success, failure);
+  }
+
+  /**
+   * Retrieves the base64-encoded data for an image in the ImageStore. If the
+   * specified URI does not match an image in the store, the failure callback
+   * will be called.
+   *
+   * Note that it is very inefficient to transfer large quantities of binary
+   * data between JS and native code, so you should avoid calling this more
+   * than necessary. To display an image in the ImageStore, you can just pass
+   * the URI to an `<Image/>` component; there is no need to retrieve the
+   * base64 data.
+   */
+  static getBase64ForTag(
+    uri: string,
+    success: (base64ImageData: string) => void,
+    failure: (error: any) => void
+  ) {
+    RCTImageStoreManager.getBase64ForTag(uri, success, failure);
+  }
+}
+
+module.exports = ImageStore;