Give karma.config.js access to command line arguments

[danielsiwiec]

Currently, the config argument passed into karma.config.js is an empty object, that gets filled out. It would be beneficial, to have access to command line arguments from within the configuration, through the passed config object, as this would allow custom logic, based on those arguments to be applied.

Example scenario: There are two test suites (eg. unit and component) in two different folders. It's desired to run only the selected test suite. This could easily be achieved by passing an argument on the command line (like suite=unit), that karma.config.js would have access to and would set the proper value on the config.files property.

What do people think about it? The implementation of this would be very straightforward (basically a one-liner).

[dtabuenc]

This would definitely be useful, such as for turning on/off coverage instrumentation via commandline when using non-standard processors like webpack.

[dignifiedquire]

I agree, and can see how this could be useful. If someone wants to work on this I'd be happy to accept a PR

[danielsiwiec]

Cool. I'll submit a PR for this. Thanks!

[naganowl]

A workaround that currently exists would is #61 (comment).

I'm planning on using the suggestion in order to toggle coverage as @dtabuenc mentioned.

[danielsiwiec]

PR submitted

[dignifiedquire]

@danielsiwiec could you make a PR with some docs about this please? Thanks

[danielsiwiec]

Good idea. Will do shortly

[JamieMason]

Thanks @dignifiedquire @danielcompton.

I figured out after posting that it's mentioned in the OP (resolved config is under config.*).