Add support for coverage files relative to shifter config#101
Add support for coverage files relative to shifter config#101andrewnicols wants to merge 1 commit intoyui:masterfrom
Conversation
|
This is already supported, probably not well documented though, but you should be able to add this to your and shifter will automatically resolve that relative to the |
|
Hi Caridy, Unfortunately not for recursive builds where the build-dir is relative to See #66 which forcibly sets the build-dir to a relative path on recursive On 5 September 2013 02:08, Caridy Patino notifications@github.com wrote:
|
I've recently been trying to build coverage reports from shifted modules and hit this issue on the way.
At present, all coverage files are built with the name and filename set as:
When istanbul then comes along to produce the report, it tries to find the source files at this path; however, when building in a recursive or distributed situation and where build is not in your immediate path, this leads to unresolvable .js files.
This change sets an internal relativeTo option to shifter which is then used when instrumenting the -coverage.js files so that each file is built relative to the configuration. This is only done when the configuration file:
coverageRelativeToConfig: trueIn a nested structure such as:
Instead of the path being set to:
It will be set to
When it comes to creating the istanbul reports, this is now resolvable.