-
Notifications
You must be signed in to change notification settings - Fork 609
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add duration flag (in seconds) to scan with options #967
Conversation
This allows different scan modes to be easily selected while still allowing the scan to be time-limited
002301f
to
6d507fd
Compare
Looks like you're cutting off the 'scan' function, which will force all consumers of that to switch. Do you normally want a deprecation period to ease people over? I.e., change 'scan' to internally call 'startScanWithOptions'. Also, will this be available in the 'slim' variant? BTW, here is my code to replace the 'scan' call. I believe I am seeing the same scan performance with it as before the API change you indicated! |
Both |
Ah, that's what I was expecting! Sorry. |
Slim runs on a different branch. I'll publish both at the same time once I merge this 🙂 |
…started The this::stopScan syntax seems to lose the exact reference for the runnable, preventing the remove callback from properly clearing it.
df6929e
to
7a3db00
Compare
7a3db00
to
4601ef1
Compare
4601ef1
to
3946f97
Compare
This allows different scan modes to be easily selected while still allowing the scan to be time-limited