Support for passing configPath and coverageSummaryPath

[Koleok]

closes #1 closes #2

[shercoder]

Hi @Koleok,
I'm having an issue regarding this change. I'm using jest.config.json that defines thresholds as well. After running jest coverage and then ratchet with --configPath=jest.config.json, it adds thresholds to our package.json instead of updating thresholds in our jest.config.json.

Is this intended behavior? or am I doing something wrong running ratchet?

[Koleok]

@shercoder First off you are not doing anything wrong, and yes It would make perfect sense for the ratcheted thresholds to be written back to your config file at the specified path.

When I first wrote this I just didn't have a need to handle case of using a jest config file, so I figured I'd just wait around and see if anyone else asked. So this is valuable feedback ✨

I can probably slice off an hour or so and make this change this week thanks for the input 👍

[shercoder]

@Koleok Hey thanks for replying. Yeah I think it would be very much valuable to add this feature.