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

fix: already-handled spelling [v13] #7813

Merged
merged 30 commits into from Dec 9, 2021

Conversation

benallfree
Copy link
Contributor

@benallfree benallfree commented Nov 29, 2021

What kind of change does this PR introduce?

Spelling error fix for intercept constant

Fixes: #7745, #7747, #7780

Did you add tests for your changes?

Updated tests

If relevant, did you update the documentation?

Yes

Summary

Somehow a silly (and breaking) spelling error made it into release :)

Does this PR introduce a breaking change?

Yes. Recommend release with v13

benallfree and others added 22 commits November 24, 2021 12:56
Co-authored-by: Rodrigo Fernández <fdez.romero@gmail.com>
Co-authored-by: Rodrigo Fernández <fdez.romero@gmail.com>
Co-authored-by: Rodrigo Fernández <fdez.romero@gmail.com>
Co-authored-by: Rodrigo Fernández <fdez.romero@gmail.com>
Co-authored-by: Rodrigo Fernández <fdez.romero@gmail.com>
Co-authored-by: Rodrigo Fernández <fdez.romero@gmail.com>
…/puppeteer into expose-intercept-resolution-2
…/puppeteer into expose-intercept-resolution-2
@benallfree benallfree changed the title [v13] fix: already-handled spelling fix fix: already-handled spelling [v13] Dec 7, 2021
@OrKoN OrKoN enabled auto-merge (squash) December 9, 2021 14:39
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Should HTTPRequest's interceptResolution be public?
2 participants