allow the directory that coverage reports are outputted to to be configured

[bcoe]

fixes #63

reviewers: @jbcpollak, @mateatslc, @jamestalmage

[jamestalmage]

The code looks fine. I'm still not sold as to why it's necessary. Do people have real reasons they need to rename the directory? I haven't heard anybody say "Without this option it's impossible/difficult to use NYC, because...".

This sort of option isn't bad in itself, but allowing them to accumulate unchecked just bloats the codebase, creates more potential failure points, and just slows development of meaningful features. If there is legitimate need, then by all means 👍.

[jbcpollak]

The reason I needed to relocate the output was to conform to the
requirements of our CI service (circleci) which needs reports in a specific
directory.

On Mon, Jan 18, 2016, 11:34 PM James Talmage [email protected]
wrote:

The code looks fine. I'm still not sold as to why it's necessary. Do
people have real reasons they need to rename the directory? I haven't heard
anybody say "Without this option it's impossible/difficult to use NYC,
because...".

This sort of option isn't bad in itself, but allowing them to accumulate
unchecked just bloats the codebase, creates more potential failure points,
and just slows development of meaningful features. If there is legitimate
need, then by all means [image: 👍].

—
Reply to this email directly or view it on GitHub
#145 (comment).

[jamestalmage]

Sold.

[mateatslc]

My reason for this is similar to @jbcpollak's, help CI process find the report. This does exactly what I needed, thanks!