Disable TS diagnostics for the test cases not being run

[slikts]

Issue :

I'm doing refactoring and I get a ton of compile errors, which is fine, but I'm starting with a specific test suite by filtering out the other test files, but I'm still getting flooded with the TS compile errors from the other files.

Expected behavior :

It doesn't need to show compile errors from test suites that aren't being run.

Debug log:

log file content

# content of ts-jest.log :

Minimal repo :

[slikts]

I've worked around this by temporarily disabling diagnostics.

[huafu]

Sorry @slikts but this is kinda impossible. jest calls transform() of ts-jest for ANY file which is imported, how to know if this file is a source file depending on the test file being run? Or did I miss-understood?

I'm going to close this for now as a wont fix, but if you know or think of a solution for that, please re-open and explain.

[inoyakaigor]

jest calls transform() of ts-jest for ANY file which is imported

@huafu Does this mean that this is the reason why I got this error?

[huafu]

Nope, here you're missing a transformer for styl files in your jest config. So it tries to load index.styl.js, index.styl.ts, .... But for this, you'll have to look at jest configuration as it is unrelated to ts-jest. Look at jest transform option.

[slikts]

I've ran into this again, and I don't understand what the workflow is supposed to be; if I'm refactoring a specific part of the code, the test suite becomes unusable, because it's flooded with errors like unused values elsewhere, and filtering the tests doesn't help.