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

Follow up about Jest issues #3794

Open
2 tasks
gaearon opened this issue Jan 14, 2018 · 2 comments
Open
2 tasks

Follow up about Jest issues #3794

gaearon opened this issue Jan 14, 2018 · 2 comments

Comments

@gaearon
Copy link
Contributor

gaearon commented Jan 14, 2018

Before cutting 2.0 final I'd like to have a good understanding of these:

@gaearon gaearon added this to the 2.0.0 milestone Jan 14, 2018
@gaearon
Copy link
Contributor Author

gaearon commented Jan 14, 2018

cc @SimenB

@SimenB
Copy link
Contributor

SimenB commented Jan 15, 2018

The first is indeed a regression of sorts, although I'm unsure how to handle it in a way that satisfies all parties. I do think it's more important to not silently pass tests creating rejected promises than allowing you to asynchronously attach catch. But I do understand it's something that could be useful.

I've responded to the second issue, that feels more like a bug.

@Timer Timer modified the milestones: 2.0.x, 2.x Sep 26, 2018
@iansu iansu modified the milestones: 2.x, 3.x Mar 10, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants