-
Notifications
You must be signed in to change notification settings - Fork 461
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
add tests for Promise.withResolvers proposal #3867
Conversation
Co-authored-by: Jordan Harband <ljharb@gmail.com>
Now Stage 3. |
Co-authored-by: Jordan Harband <ljharb@gmail.com>
Co-authored-by: Jordan Harband <ljharb@gmail.com>
Co-authored-by: Jordan Harband <ljharb@gmail.com>
Co-authored-by: Ms2ger <Ms2ger@gmail.com>
Co-authored-by: Linus Groh <mail@linusgroh.de>
Thanks for contributing this! Would you mind opening a tracking issue? An example is #3756. You don't have to write the whole testing plan, someone else can help with that, but we should use one to verify that we're covering everything in the proposal. I haven't looked too closely at this PR yet so I might be missing something, but it seems like there are some cases particularly with subclassing We also need to add the standard boilerplate tests for built-in APIs. For an example, see We don't have to block reviewing and merging this PR on complete coverage, the other tests can come in following PRs, but we should keep track in the tracking issue of what's been merged. |
Could we have this merged soon for shipping in Chrome? |
sorry for the delay with this.
|
Thanks, @peetklecha. The failing CI job is #3891, we really should remove the job until that's fixed. I'll merge this now, and add some suggestions to the tracking issue you opened. |
This shouldn't be merged yet as Promise.withResolvers is still only Stage 2.