-
Notifications
You must be signed in to change notification settings - Fork 63
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Provide the ability to add arbitrary Karma plugins #43
Comments
Tricky. If doo every supports something like this, it will probably follow the last option, a merged in config. To see if this is needed, we should first explore/solve #34 either through docs or features and after that think about plugins in general. |
Pull request 108 hasn't been reviewed yet but it adds the ability to add arbitrary config to karma.conf.js by adding it to project.clj. :karma {:config {"reporters" ["progress", "junit"]
"plugins" ["karma-junit-reporter"]
"junitReporter" {"outputDir" "test-output"}}}
It's limited to karma tests but does help with issue #34 |
Possibility to use own karma.conf.js would allow us to work around this problem: karma-runner/karma#1344 |
I'd like to be able to add karma-junit-reporter to my karma.conf.js file. I can imagine in the long run that lots of people will all want to install their own Karma plugins. There are a few ways to accomodate this:
karma.conf.js
file to disk and then they can add their plugins, configuration, e.t.c. to that static file. The problem with this approach is regenerating it when things change, and it getting out of date.karma.conf.js
. This would be somewhat similar to how Leiningen merges profiles into the main project config.This presupposes that the Karma plugins will be able to understand the output of doo tests, I'm not sure if that's the case.
Relates to #34.
The text was updated successfully, but these errors were encountered: