We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
I've just filed this bug with grunt-karma, karma-runner/grunt-karma#79
Which got me thinking, should config have a public API?
If it did, grunt-karma could parse the config itself, do whatever merging/overwriting of config it needed to, and then pass that to karma.server.
The text was updated successfully, but these errors were encountered:
The original issue was fixed, I don't think there is a need for exposing an api for that at the moment.
Sorry, something went wrong.
No branches or pull requests
I've just filed this bug with grunt-karma,
karma-runner/grunt-karma#79
Which got me thinking, should config have a public API?
If it did, grunt-karma could parse the config itself, do whatever merging/overwriting of config it needed to, and then pass that to karma.server.
The text was updated successfully, but these errors were encountered: