Fix linter issue

This commit is contained in:
Tim Wang
2017-11-04 22:01:22 +08:00
parent 972f126ed0
commit e6a22d9c00
+51 -48
View File
@@ -6879,13 +6879,13 @@ export interface NetInfoStatic {
*/
isConnected: {
fetch: () => Promise<boolean>
fetch: () => Promise<boolean>
/**
* eventName is expected to be `change`(deprecated) or `connectionChange`
*/
addEventListener: (eventName: string, listener: (result: boolean) => void) => void
/**
* eventName is expected to be `change`(deprecated) or `connectionChange`
*/
@@ -8113,52 +8113,55 @@ export interface ImagePickerIOSStatic {
}
export interface ImageStoreStatic {
/**
* Check if the ImageStore contains image data for the specified URI.
* @platform ios
*/
hasImageForTag(uri: string, callback: (hasImage: boolean) => void): void
/**
* 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
*/
removeImageForTag(uri: string): void
/**
* 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.
* @platform ios
*/
addImageFromBase64(
base64ImageData: string,
success: (uri: string) => void,
failure: (error: any) => void
): void
/**
* 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.
*/
getBase64ForTag(
uri: string,
success: (base64ImageData: string) => void,
failure: (error: any) => void
): void
/**
* Check if the ImageStore contains image data for the specified URI.
* @platform ios
*/
hasImageForTag(uri: string, callback: (hasImage: boolean) => void): void
/**
* 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
*/
removeImageForTag(uri: string): void
/**
* 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.
* @platform ios
*/
addImageFromBase64(
base64ImageData: string,
success: (uri: string) => void,
failure: (error: any) => void
): void
/**
* 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.
*/
getBase64ForTag(
uri: string,
success: (base64ImageData: string) => void,
failure: (error: any) => void
): void
}
//