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.

Sign up for GitHub

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

Jump to bottom

Jest drop of mapCoverage #444

Closed
manu-st opened this issue Feb 16, 2018 · 2 comments
Closed

Jest drop of mapCoverage #444

manu-st opened this issue Feb 16, 2018 · 2 comments

Comments

@manu-st
Copy link

manu-st commented Feb 16, 2018

This is not an issue per say but I noticed that jest is dropping the mapCoverage option:
jestjs/jest#5177
and I was wondering what will the effect be for user of ts-jest since we rely on this option to have a proper map of our TypeScript code coverage?
@kulshekhar
Copy link
Owner

It should continue working. If anything, it's supposedly better (reference: #340 (comment))

@manu-st
Copy link
Author

manu-st commented Feb 16, 2018

This sounds great. We have been facing issues with inconsistent mapcoverage (i.e. two machine using the same code but reporting different coverage). I wonder if this will solve this situation.

@manu-st manu-st closed this as completed Feb 16, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@kulshekhar @manu-st