From d51a041bea892d2bead53f72eaf4553abc9faca3 Mon Sep 17 00:00:00 2001 From: MacKentoch Date: Mon, 20 Mar 2017 13:54:12 +0100 Subject: [PATCH] update monitoring and ranging md files --- examples/samples/monitoring.ios.md | 2 +- examples/samples/ranging.ios.md | 11 +++++++---- 2 files changed, 8 insertions(+), 5 deletions(-) diff --git a/examples/samples/monitoring.ios.md b/examples/samples/monitoring.ios.md index 839f06d0..1138338a 100644 --- a/examples/samples/monitoring.ios.md +++ b/examples/samples/monitoring.ios.md @@ -17,7 +17,7 @@ If you don't: > For monitoring you don't have the choice you have to request `Always` authorization wether you need background mode or not. -[See matching lines in sample example]() +[See matching lines in sample example](https://github.com/MacKentoch/react-native-beacons-manager/blob/master/examples/samples/monitoring.ios.js#L36) ### 1 `Beacons.requestAlwaysAuthorization();` (**background and foreground use-case**) diff --git a/examples/samples/ranging.ios.md b/examples/samples/ranging.ios.md index 08648612..07942c14 100644 --- a/examples/samples/ranging.ios.md +++ b/examples/samples/ranging.ios.md @@ -18,7 +18,6 @@ If you don't: You can request 2 kind of authorizations depending on the use case: > Do you need background capability or not? -[See matching lines in sample example](https://github.com/MacKentoch/react-native-beacons-manager/blob/master/examples/samples/ranging.ios.js#L35) ### 1.a `Beacons.requestWhenInUseAuthorization();` (**foreground** only use-case) @@ -29,6 +28,8 @@ Ensure to call Beacons.requestWhenInUseAuthorization(); ``` +[See matching lines in sample example](https://github.com/MacKentoch/react-native-beacons-manager/blob/master/examples/samples/ranging.ios.js#L35) + #### in your iOS project To be effective your `info.plist` file should have `Privacy - Location When In Use Usage Description` key defined (*empty value or not. It is better to define a value to a custom / more user-friendly message*). @@ -49,6 +50,8 @@ Ensure to call Beacons.requestAlwaysAuthorization(); ``` +[See matching lines in sample example](https://github.com/MacKentoch/react-native-beacons-manager/blob/master/examples/samples/ranging.ios.js#L35) + #### in your iOS project To be effective your `info.plist` file should have `Privacy - Location Always Usage Description` key defined (*empty value or not. It is better to define a value to a custom / more user-friendly message*). @@ -72,7 +75,7 @@ const region = { identifier, uuid }; Beacons.startRangingBeaconsInRegion(region); ``` -[See matching lines in sample example](https://github.com/MacKentoch/react-native-beacons-manager/blob/master/examples/samples/ranging.ios.js#L40) +[See matching lines in sample example](https://github.com/MacKentoch/react-native-beacons-manager/blob/master/examples/samples/ranging.ios.js#L41) ## 3- register events @@ -105,7 +108,7 @@ Note: beacons is an array of object: } ``` -[See matching lines in sample example](https://github.com/MacKentoch/react-native-beacons-manager/blob/master/examples/samples/ranging.ios.js#L55) +[See matching lines in sample example](https://github.com/MacKentoch/react-native-beacons-manager/blob/master/examples/samples/ranging.ios.js#L50) ## 4- on componentWillUnMount: unregister events and stop ranging @@ -121,4 +124,4 @@ Beacons.stopRangingBeaconsInRegion(); DeviceEventEmitter.remove(); ``` -[See matching lines in sample example](https://github.com/MacKentoch/react-native-beacons-manager/blob/master/examples/samples/ranging.ios.js#L64) +[See matching lines in sample example](https://github.com/MacKentoch/react-native-beacons-manager/blob/master/examples/samples/ranging.ios.js#L61)