-
Notifications
You must be signed in to change notification settings - Fork 215
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
fix: wrap onRequestFinished
to use promises
#250
Conversation
CI seems to be having a versioning error with Chrome that seems to be unrelated to this PR? |
I'll take care of that in #251 |
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.
LGTM thanks. I'll merge it after the other PR that unbreaks the build is merged.
The other PR got approved and merged. Could you rebase and update the PR so we can get a green CI build? |
Fixes #249. This updates `browser.devtools.network.onRequestFinished` to emit an object with a promisified `getContent()` property. This brings the polyfill implementation in line with Firefox's implementation, although MDN documentation is still inaccurate at the moment. Also updates some out of date documentation with `makeCallback()` and `wrapAsyncFunction()`.
Rebased and got a green CI, thanks for fixing that. Should be ready to merge. |
Thanks for the report and patch! |
Thanks so much for the patch, @dgp1130! Your contribution has been added to our recognition wiki. Take care! |
Fixes #249.
This updates
browser.devtools.network.onRequestFinished
to emit anobject with a promisified
getContent()
property. This brings thepolyfill implementation in line with Firefox's implementation, although
documentation is still inaccurate at the moment.
Also updates some out of date documentation with
makeCallback()
.I tested this in my own Chrome extension and it appears to work as expected.