-
Notifications
You must be signed in to change notification settings - Fork 16.2k
feat: promisify contentTracing recording APIs #16584
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
Conversation
4615ef4
to
1b769c9
Compare
d5f9023
to
62afad9
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I love the improvements you made here to lib/browser/api/content-tracing.js
62afad9
to
0d50720
Compare
Release Notes Persisted
|
I was unable to backport this PR to "5-0-x" cleanly; |
* feat: promisify contentTracing.startRecording() * feat: promisify contentTracing.stopRecording() * test: convert specs for new promisified apis * chore: deprecate and ensure legacy tests work
* feat: promisify contentTracing.startRecording() * feat: promisify contentTracing.stopRecording() * test: convert specs for new promisified apis * chore: deprecate and ensure legacy tests work
* feat: promisify contentTracing.startRecording() * feat: promisify contentTracing.stopRecording() * test: convert specs for new promisified apis * chore: deprecate and ensure legacy tests work
Description of Change
Promisify
contentTracing.startRecording()
andcontentTracing.stopRecording()
cc @ckerr @deepak1556
Checklist
npm test
passesRelease Notes
Notes: Converted
contentTracing.startRecording()
andcontentTracing.stopRecording()
to return a promise instead taking a callback.