-
Notifications
You must be signed in to change notification settings - Fork 41
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
Provide both Sync and Async JS APIs #1373
Conversation
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.
Thanks for this quick turnaround on this. Generally LGTM.
I do think it's worth keeping the sync examples too 👍 Looks like you're still working on the workflow for them so I'll rereview it once you've resolved the issue.
1ecf50c
to
48e4dee
Compare
b987414
to
770f2ae
Compare
We won't document this, and we can remove it.
The reason behind this is that the E2E tests take huge resource on Github and become more flaky when run together both with sync and async examples. Since we're using a weak Github runner.
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.
This is awesome! Thanks! LGTM 🚀
What?
Provides sync and async APIs within the same module.
k6/x/browser
-> maps to sync JS APIk6/x/browser/async
-> maps to async JS APIWhy?
Plan
I'll create issues for this.
Checklist
Related PR(s)/Issue(s)
#1117 #428