API-parity with react-native-ibeacon

[mmazzarolo]

• Ranging output (More info here: Use the same standard of react-native-ibeacons for the ranging output events #5 and Add the proximity info on ranging response #6)
• Monitoring output (needs testing)
• Region parameter should be an object
• API method name startRangingBeaconsInRegion
• API method name stopRangingBeaconsInRegion
• API method name startMonitoringForRegion
• API method name stopMonitoringForRegion
• API even name beaconsDidRange
• API even name regionDidEnter
• API even name regionDidExit

[mmazzarolo]

Info on ranging output

Current ranging output from react-native-beacons-android:

{
  region: {
    identifier: String,
    uuid: String
  },
  beacons: [
    {
       uuid: String, 
       major: Number, 
       minor: Number, 
       rssi: Number, 
       proximity: Number, // Custom proximity
       distance: Number // Unavailable on iOS
    }
  ]
}

Current ranging output from react-native-ibeacons:

{
  region: {
    identifier: String,
    uuid: String
  },
  beacons: [
    {
       uuid: String, 
       major: Number, 
       minor: Number, 
       rssi: Number, 
       proximity: String, // It seems to be unavailable on Android
       accuracy: Number // It seems to be unavailable on Android
    }
  ]
}

Info on proximity

The proximity field in the output of react-native-beacons-android is calculated this way:

private String getProximity(double distance) {
        if (distance == -1.0) {
            return "unknown";
        } else if (distance < 1) {
            return "immediate";
        } else if (distance < 3) {
            return "near";
        } else {
            return "far";
        }
    }

More info here: #5 and #6

[JonasWho]

I've send a pull request for the monitoring part. I have it working in my project with simultaneous monitoring of two different regions on a OnePlus E1003 with Android 5.1.1 and a Galaxy A5 with 6.0.1

[mmazzarolo]

Thanks man, merged :) I'll publish it on npm soon