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
When a framework is defined as a factory, it used to be called for its actions to be considered.
See below for a simple instance :
function Fmk(logger) { logger.info('It works !'); } Fmk.$inject = ['logger']; module.exports = { 'framework:Fmk': ['factory', Fmk]};
The framework is ignored. The framework index file is still being read.
karma --version
karma.config.js
It works !
The text was updated successfully, but these errors were encountered:
It seems like karma-jasmine works as a framework factory: https://github.com/karma-runner/karma-jasmine/blob/master/lib/index.js
Sorry, something went wrong.
I can't tell. I can't find any evidence this was a supported feature. There is no documentation when it comes to plugin development.
I just ran into an issue where the karma-detect-browsers plugin stopped working and in fact wasn't even called. That's the issue I simplified.
Maybe you can look at this test to see why your case is different: https://github.com/karma-runner/karma/tree/master/test/e2e/support/middleware
No branches or pull requests
Expected behaviour
When a framework is defined as a factory, it used to be called for its actions to be considered.
See below for a simple instance :
Actual behaviour
The framework is ignored. The framework index file is still being read.
Environment Details
karma --version
): 2.0.2karma.config.js
file : see aboveSteps to reproduce the behaviour
It works !
message.The text was updated successfully, but these errors were encountered: