You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the current README we have the following description of the .start method:
start(options)
Init the module. Returns a Promise object. Don't call this multiple times.
also...
Note
Remember to use the start method before anything.
Question
We are currently using this library in an application that has multiple entry points where bluetooth is required. These entry points are not always hit by a user and therefore it does not feel appropriate to invoke BleManager.start(..) at the very beginning of the lifecycle of the app. Ideally we would only initiate the module upon the actual need of Bluetooth. So in order to do this and adhere to the above notes we do the following:
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
In the current README we have the following description of the
.start
method:also...
Question
We are currently using this library in an application that has multiple entry points where bluetooth is required. These entry points are not always hit by a user and therefore it does not feel appropriate to invoke
BleManager.start(..)
at the very beginning of the lifecycle of the app. Ideally we would only initiate the module upon the actual need of Bluetooth. So in order to do this and adhere to the above notes we do the following:ble-manager-utils.ts:
Is there any particular reason / use-case why this logic cannot be abstracted away in the library itself? It feels like an unnecessary administration.
Beta Was this translation helpful? Give feedback.
All reactions