Skip to content
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

Expose #client via _client() on HTTPRequest #8545

Closed
wants to merge 2 commits into from

Conversation

smashah
Copy link

@smashah smashah commented Jun 22, 2022

What kind of change does this PR introduce?

A small change that will allow the puppeteer-page-proxy project a path to working again with the latest versions of puppeteer

Did you add tests for your changes?

_client() is not documented on Page yet still exists so I guess it's not required.

Summary

Completely eliminating access to the HTTPRequest._client property will break puppeteer-page-proxy and in turn negatively affect my users. Forcing my project to use older puppeteer version will also negatively affect my users. I am making this PR so I can eventually make a PR/fork on puppeteer-page-proxy

open-wa/wa-automate-nodejs#2755
Cuadrix/puppeteer-page-proxy#78

Does this PR introduce a breaking change?

No

Other information

This will allow the puppeteer-page-proxy project a path to working again with the latest versions of puppeteer
This keeps in line with the method call on `Page`
@smashah smashah changed the title Expose #client via client() on HTTPRequest Expose #client via _client() on HTTPRequest Jun 22, 2022
@jrandolf
Copy link
Contributor

Fixed in #8556

@jrandolf jrandolf closed this Jun 23, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants