Closed k-rajat19 closed 1 month ago
Name | Link |
---|---|
Latest commit | b2f9112e92ba399d9d8ea89a70fa87d3c8de82c0 |
Latest deploy log | https://app.netlify.com/sites/jestjs/deploys/66b8a8ef3903ee0008e6c3b0 |
Deploy Preview | https://deploy-preview-15232--jestjs.netlify.app |
Preview on mobile | Toggle QR Code...Use your smartphone camera to open QR code link. |
To edit notification comments on pull requests, go to your Netlify site configuration.
That's just because all CLI arguments are strings. But we probably don't need to say that in the types, so real fix is probably to remove it from there?
That's just because all CLI arguments are strings. But we probably don't need to say that in the types, so real fix is probably to remove it from there?
that sounds more reasonable but it will be breaking for those who are already passing string? that's why I thought to make change in the doc instead of changing types 😅
I doubt anybody's passing it, but if they do, it should be easy enough to change. This only changes the types anyways.
Mind adding a changelog entry?
This pull request has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. Please note this issue tracker is not a help forum. We recommend using StackOverflow or our discord channel for questions.
Summary
According to types
testFailureExitCode
can also take string values.Test plan
Green CI