Update dependencies + format

Author: zoontek

.flowconfig

@@ -1,9 +1,99 @@
 [ignore]
+; We fork some components by platform
+.*/*[.]android.js
+
+; Ignore "BUCK" generated dirs
+<PROJECT_ROOT>/\.buckd/
+
+; Ignore unexpected extra "@providesModule"
+.*/node_modules/.*/node_modules/fbjs/.*
+
+; Ignore duplicate module providers
+; For RN Apps installed via npm, "Libraries" folder is inside
+; "node_modules/react-native" but in the source repo it is in the root
+example/node_modules/react-native/Libraries/react-native/React.js
+
+; Ignore polyfills
+example/node_modules/react-native/Libraries/polyfills/.*
+
+; These should not be required directly
+; require from fbjs/lib instead: require('fbjs/lib/warning')
+example/node_modules/warning/.*
+
+; Flow doesn't support platforms
+.*/Libraries/Utilities/HMRLoadingView.js
+
+[untyped]
+.*/node_modules/@react-native-community/cli/.*/.*
 
 [include]
 
 [libs]
+example/node_modules/react-native/Libraries/react-native/react-native-interface.js
+example/node_modules/react-native/flow/
+
+[options]
+emoji=true
+
+esproposal.optional_chaining=enable
+esproposal.nullish_coalescing=enable
+
+module.file_ext=.js
+module.file_ext=.json
+module.file_ext=.ios.js
+
+module.system=haste
+module.system.haste.use_name_reducers=true
+# get basename
+module.system.haste.name_reducers='^.*/\([a-zA-Z0-9$_.-]+\.js\(\.flow\)?\)$' -> '\1'
+# strip .js or .js.flow suffix
+module.system.haste.name_reducers='^\(.*\)\.js\(\.flow\)?$' -> '\1'
+# strip .ios suffix
+module.system.haste.name_reducers='^\(.*\)\.ios$' -> '\1'
+module.system.haste.name_reducers='^\(.*\)\.android$' -> '\1'
+module.system.haste.name_reducers='^\(.*\)\.native$' -> '\1'
+module.system.haste.paths.blacklist=.*/__tests__/.*
+module.system.haste.paths.blacklist=.*/__mocks__/.*
+module.system.haste.paths.whitelist=<PROJECT_ROOT>/example/node_modules/react-native/Libraries/.*
+module.system.haste.paths.whitelist=<PROJECT_ROOT>/example/node_modules/react-native/RNTester/.*
+module.system.haste.paths.whitelist=<PROJECT_ROOT>/example/node_modules/react-native/IntegrationTests/.*
+module.system.haste.paths.blacklist=<PROJECT_ROOT>/example/node_modules/react-native/Libraries/react-native/react-native-implementation.js
+module.system.haste.paths.blacklist=<PROJECT_ROOT>/example/node_modules/react-native/Libraries/Animated/src/polyfills/.*
+
+munge_underscores=true
+
+module.name_mapper='^[./a-zA-Z0-9$_-]+\.\(bmp\|gif\|jpg\|jpeg\|png\|psd\|svg\|webp\|m4v\|mov\|mp4\|mpeg\|mpg\|webm\|aac\|aiff\|caf\|m4a\|mp3\|wav\|html\|pdf\)$' -> 'RelativeImageStub'
+
+suppress_type=$FlowIssue
+suppress_type=$FlowFixMe
+suppress_type=$FlowFixMeProps
+suppress_type=$FlowFixMeState
+
+suppress_comment=\\(.\\|\n\\)*\\$FlowFixMe\\($\\|[^(]\\|(\\(<VERSION>\\)? *\\(site=[a-z,_]*react_native\\(_ios\\)?_\\(oss\\|fb\\)[a-z,_]*\\)?)\\)
+suppress_comment=\\(.\\|\n\\)*\\$FlowIssue\\((\\(<VERSION>\\)? *\\(site=[a-z,_]*react_native\\(_ios\\)?_\\(oss\\|fb\\)[a-z,_]*\\)?)\\)?:? #[0-9]+
+suppress_comment=\\(.\\|\n\\)*\\$FlowExpectedError
 
 [lints]
+sketchy-null-number=warn
+sketchy-null-mixed=warn
+sketchy-number=warn
+untyped-type-import=warn
+nonstrict-import=warn
+deprecated-type=warn
+unsafe-getters-setters=warn
+inexact-spread=warn
+unnecessary-invariant=warn
+signature-verification-failure=warn
+deprecated-utility=error
 
-[options]
+[strict]
+deprecated-type
+nonstrict-import
+sketchy-null
+unclear-type
+unsafe-getters-setters
+untyped-import
+untyped-type-import
+
+[version]
+^0.98.0

README.md

@@ -20,12 +20,12 @@ _Complies with
 
 ## ⚠️ Breaking changes in version 1.0.0
 
-* Now using React Native's own JS `PermissionsAndroid` module on Android, which
+- Now using React Native's own JS `PermissionsAndroid` module on Android, which
   is great because we no longer have to do any additional linking on Android
-* Updated API to be closer to React Native's `PermissionsAndroid`
-* Removed `openSettings()` support on Android (to stay linking-free). There are
+- Updated API to be closer to React Native's `PermissionsAndroid`
+- Removed `openSettings()` support on Android (to stay linking-free). There are
   several NPM modules available for this
-* `restricted` status now supported on Android, although it means something
+- `restricted` status now supported on Android, although it means something
   different than iOS
 
 ## Setup
@@ -62,13 +62,12 @@ react-native link react-native-permissions
    folder ➜ `Add Files to <...>`
 2. Go to `node_modules` ➜ `react-native-permissions` ➜ select
    `ReactNativePermissions.xcodeproj`
-3. Add `libReactNativePermissions.a` to `Build Phases` -> `Link Binary With
-   Libraries`
+3. Add `libReactNativePermissions.a` to `Build Phases` -> `Link Binary With Libraries`
 
 ## Using
 
 ```js
-import Permissions from 'react-native-permissions'
+import Permissions from 'react-native-permissions';
 // OR const Permissions = require('react-native-permissions').default
 // if you use CommonJS module system
 
@@ -81,18 +80,18 @@ export default class extends React.Component {
   componentDidMount() {
     Permissions.check('photo').then(response => {
       // Response is one of: 'authorized', 'denied', 'restricted', or 'undetermined'
-      this.setState({ photoPermission: response })
-    })
+      this.setState({photoPermission: response});
+    });
   }
 
   // Request permission to access photos
   _requestPermission = () => {
     Permissions.request('photo').then(response => {
       // Returns once the user has chosen to 'allow' or to 'not allow' access
       // Response is one of: 'authorized', 'denied', 'restricted', or 'undetermined'
-      this.setState({ photoPermission: response })
-    })
-  }
+      this.setState({photoPermission: response});
+    });
+  };
 
   // Check the status of multiple permissions
   _checkCameraAndPhotos = () => {
@@ -101,9 +100,9 @@ export default class extends React.Component {
       this.setState({
         cameraPermission: response.camera,
         photoPermission: response.photo,
-      })
-    })
-  }
+      });
+    });
+  };
 
   // This is a common pattern when asking for permissions.
   // iOS only gives you once chance to show the permission dialog,
@@ -122,10 +121,10 @@ export default class extends React.Component {
           style: 'cancel',
         },
         this.state.photoPermission == 'undetermined'
-          ? { text: 'OK', onPress: this._requestPermission }
-          : { text: 'Open Settings', onPress: Permissions.openSettings },
+          ? {text: 'OK', onPress: this._requestPermission}
+          : {text: 'Open Settings', onPress: Permissions.openSettings},
       ],
-    )
+    );
   }
 
   //...
@@ -141,7 +140,7 @@ Promises resolve into one of these statuses:
 | Return value   | Notes                                                                                                                                                                                                                                                                  |
 | -------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
 | `authorized`   | User has authorized this permission                                                                                                                                                                                                                                    |
-| `denied`       | User has denied this permission at least once. On iOS this means that the user will not be prompted again. Android users can be prompted multiple times until they select 'Never ask me again'                                                                          |
+| `denied`       | User has denied this permission at least once. On iOS this means that the user will not be prompted again. Android users can be prompted multiple times until they select 'Never ask me again'                                                                         |
 | `restricted`   | **iOS** - this means user is not able to grant this permission, either because it's not supported by the device or because it has been blocked by parental controls. **Android** - this means that the user has selected 'Never ask me again' while denying permission |
 | `undetermined` | User has not yet been prompted with a permission dialog                                                                                                                                                                                                                |
 
@@ -182,40 +181,39 @@ The current supported permissions are:
 
 ### iOS Notes
 
-* Permission type `bluetooth` represents the status of the
+- Permission type `bluetooth` represents the status of the
   `CBPeripheralManager`. Don't use this if you only need `CBCentralManager`.
-* Permission type `location` accepts a second parameter for `request()` and
+- Permission type `location` accepts a second parameter for `request()` and
   `check()`; the second parameter is a string, either `always` or `whenInUse`
   (default).
-* Permission type `notification` accepts a second parameter for `request()`. The
+- Permission type `notification` accepts a second parameter for `request()`. The
   second parameter is an array with the desired alert types. Any combination of
   `alert`, `badge` and `sound` (default requests all three).
-* If you are not requesting mediaLibrary then you can remove MediaPlayer.framework from the xcode project.
+- If you are not requesting mediaLibrary then you can remove MediaPlayer.framework from the xcode project.
 
 ```js
 // example
-Permissions.check('location', { type: 'always' }).then(response => {
-  this.setState({ locationPermission: response })
-})
+Permissions.check('location', {type: 'always'}).then(response => {
+  this.setState({locationPermission: response});
+});
 
-Permissions.request('location', { type: 'always' }).then(response => {
-  this.setState({ locationPermission: response })
-})
+Permissions.request('location', {type: 'always'}).then(response => {
+  this.setState({locationPermission: response});
+});
 
-Permissions.request('notification', { type: ['alert', 'badge'] }).then(
+Permissions.request('notification', {type: ['alert', 'badge']}).then(
   response => {
-    this.setState({ notificationPermission: response })
+    this.setState({notificationPermission: response});
   },
-)
+);
 ```
 
-* You cannot request microphone permissions on the simulator.
-* With Xcode 8, you now need to add usage descriptions for each permission you
+- You cannot request microphone permissions on the simulator.
+- With Xcode 8, you now need to add usage descriptions for each permission you
   will request. Open Xcode ➜ `Info.plist` ➜ Add a key (starting with "Privacy -
   ...") with your kit specific permission.
 
-Example: If you need Contacts permission you have to add the key `Privacy -
-Contacts Usage Description`.
+Example: If you need Contacts permission you have to add the key `Privacy - Contacts Usage Description`.
 
 <img width="338" alt="3cde3b44-7ffd-11e6-918b-63888e33f983" src="https://cloud.githubusercontent.com/assets/1440796/18713019/271be540-8011-11e6-87fb-c3828c172dfc.png">
 
@@ -248,6 +246,7 @@ So before submitting your app to the App Store, make sure that in your
 <key>NSMotionUsageDescription</key>
 <string>Some description</string>
 ```
+
 This is required because during the phase of processing in the App Store
 submission, the system detects that you app contains code to request the
 permission `X` but don't have the `UsageDescription` key and then it rejects the
@@ -260,16 +259,16 @@ You can find more information about this issue in #46.
 
 ### Android Notes
 
-* Uses React Native's own
+- Uses React Native's own
   [`PermissionsAndroid` JS API](http://facebook.github.io/react-native/docs/permissionsandroid.html).
-* All required permissions also need to be included in the `AndroidManifest.xml`
+- All required permissions also need to be included in the `AndroidManifest.xml`
   file before they can be requested. Otherwise `request()` will immediately
   return `denied`.
-* You can request write access to any of these types by also including the
+- You can request write access to any of these types by also including the
   appropriate write permission in the `AndroidManifest.xml` file. Read more
   [here](https://developer.android.com/guide/topics/security/permissions.html#normal-dangerous).
 
-* The optional rationale argument will show a dialog prompt.
+- The optional rationale argument will show a dialog prompt.
 
 ```js
 // example
@@ -281,11 +280,11 @@ Permissions.request('camera', {
       'so you can take awesome pictures.',
   },
 }).then(response => {
-  this.setState({ cameraPermission: response })
-})
+  this.setState({cameraPermission: response});
+});
 ```
 
-* Permissions are automatically accepted for **targetSdkVersion < 23** but you
+- Permissions are automatically accepted for **targetSdkVersion < 23** but you
   can still use `check()` to check if the user has disabled them from Settings.
 
 You might need to elevate the **targetSdkVersion** version in your

index.js

@@ -1,4 +1,4 @@
 // @flow
 
-import Permissions from './lib/permissions'
-export default Permissions
+import Permissions from './lib/permissions';
+export default Permissions;