Add Config per Reporter#419
Conversation
|
This is great, thanks @gossi! I spent the last few days fighting with Istanbul and nyc trying to get all my paths to be the same and ultimately settled on just manually modifying them with Would it be possible to document a bit more about what |
|
Thanks @RobbieTheWagner but I must confess, I only copy pasted things around to make my use-case work 🙈 In my project I was able to configure it for On the other hand it doesn't matter that much for that PR. Since this is very generic to have any options for any reporter. So it is up to consumers to figure out the options for each reporter. |
|
Thanks @gossi! I still think it would be nice to have some more docs about this and when to use it etc. but I do want to go ahead and get it in to unlock this. |
|
Just wanted to throw some thanks on this, I was searching for how to configure the |
I'm using codeclimate for my OSS projects. And for that to work, the code-coverage must be relative to repo-root, instead of project-root. This was easy done with the
vitestproject in there as it allowed to configure reports: https://vitest.dev/guide/reporters.html (it's also the same syntax that eslint uses to configure your rules).In
ember-cli-code-coverage, the config is always{}or "no config allowed". Now this PR adds support for the same config, thatvitestallows.I'm already using this with a patch on my OSS projects, here is one such PR pointed to the config.
It works, I can see my coverage on codeclimate and this PR brings back this support to everybody :)