Configurable lcov.info path

[ltomes]

trafficstars

Is a configurable lcov path something that is on the horizon?

I am working with a build task that builds coverage for multiple components into a structure similar to:

coverage/<component>/PhantomJS/
<component 1>/
<component 2>/

Ideally I would configure coverage per component.

Thanks for your time

[kankaristo]

+1

I'd prefer not to create a coverage/ directory in the project root especially for use with this package. Even better would be a full path to lcov.info, not just the directory it's in (in case you want to rename the file, too).

[jcape]

My scenario is similar: I have a gradle build system which automatically puts unit test results in build/reports/(target). Obviously I'd like to do build/reports/coverage to keep in consistent (and deletable with "gradle clean"), but this means maintaining a symlink to that directory in my root, which is kind of meh. Honestly, just being able to search for a file named "lcov.info" anywhere under the project would be fine.

[Virtual-felix]

I did a pull request on the repo fragglebob/atom-lcov-info which is a fork of this one with some bug fix, on which I added a setting to give a specific path to the .info file. https://github.com/fragglebob/atom-lcov-info/pull/2

[fragglebob]

I've merged this on my fork. :smile: