Closed ImanMh closed 3 years ago
A simple lint issue can stop npm run test. Do we really need to fix every single lint issue before running npm run test? Cause many times I want to try things out just to see if they work so I don't care about lint issues at that moment.
npm run test
I'd rather see lint issues and then test results.
Those aren't lint issues -- they are TS codes, i.e. they are type-checking errors.
TS
This is a key feature of ts-jest, but yes, you can turn it off. Duplicate of #681
ts-jest
Current Behavior
A simple lint issue can stop
npm run test
. Do we really need to fix every single lint issue before running npm run test? Cause many times I want to try things out just to see if they work so I don't care about lint issues at that moment.Expected behavior
I'd rather see lint issues and then test results.