- From: Tobie Langel via GitHub <sysbot+gh@w3.org>
- Date: Fri, 05 Feb 2016 17:10:36 +0000
- To: public-device-apis@w3.org
To give you some background however, the `sensorId`'s purpose was to
allow the discoverability API to provide a connection to an underlying
sensor so it than could be used to instantiate a `Sensor` subclass,
e.g.:
```js
window.sensors.discoverAllTheThings().then(sensors => {
let prox = new ProximitySensor({ sensorId: sensors[0].sensorId });
// etc.
});
```
As we're moving the discoverability to V2, one of the obvious solution
to this issue is to just remove the `sensorId` for now.
--
GitHub Notification of comment by tobie
Please view or discuss this issue at
https://github.com/w3c/sensors/issues/85#issuecomment-180445347 using
your GitHub account
Received on Friday, 5 February 2016 17:10:37 UTC