Open jyasskin opened 8 years ago
Alternately, we could have all of these use "bluetooth"
, and build the BluetoothPermissionResult
type to accommodate future extensions, possibly by renaming devices
to gattPeripherals
... or something better.
Right now, https://webbluetoothcg.github.io/web-bluetooth/#permission-api-integration defines the
"bluetooth"
permission, and https://webbluetoothcg.github.io/web-bluetooth/scanning.html#permission defines"bluetooth-le-scan"
. It's likely we'll have other Bluetooth permissions in the future:I'm thinking it doesn't make a lot of sense to use
"bluetooth"
to refer to just the GATT-client part. Maybe"bluetooth-gatt-client"
or"bluetooth-gatt-communication"
?