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

Async BrowserContext #1328

Merged
merged 16 commits into from
May 13, 2024
Merged

Async BrowserContext #1328

merged 16 commits into from
May 13, 2024

Conversation

inancgumus
Copy link
Member

What?

#1295

Checklist

  • I have performed a self-review of my code
  • I have added tests for my changes
  • I have commented on my code, particularly in hard-to-understand areas

@inancgumus inancgumus added async supports async (promises) breaking PRs that need to be mentioned in the breaking changes section of the release notes mapping k6 browser to Goja mapping related. browser context Issues and PRs related to browser context labels May 10, 2024
@inancgumus inancgumus self-assigned this May 10, 2024
@inancgumus inancgumus requested a review from ankur22 May 10, 2024 09:35
@inancgumus inancgumus marked this pull request as ready for review May 10, 2024 09:35
Copy link
Collaborator

@ankur22 ankur22 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

Base automatically changed from async/browsercontext-prepare to main-async May 13, 2024 13:37
@inancgumus inancgumus merged commit 3930903 into main-async May 13, 2024
14 checks passed
@inancgumus inancgumus deleted the async/browsercontext branch May 13, 2024 13:42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
async supports async (promises) breaking PRs that need to be mentioned in the breaking changes section of the release notes browser context Issues and PRs related to browser context mapping k6 browser to Goja mapping related.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants