-
Notifications
You must be signed in to change notification settings - Fork 12
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
reporters
in config could be a string
#45
Comments
reporters
in config could be a string
Is this a common pattern to simply specify the reporter name string as the karma.conf.js |
Hi @lucono. I don't know whether there's a common usage like that: this is the first Karma config I've seen and I don't know what the origin of it was in the codebase. I just thought I'd report it, because getting this plugin up was quite challenging with this undocumented setting. I think many people would have given up:
But, whatever you decide to do with this issue, even if you close it, it'll be searchable on The Web :) Thank you for this tool! It's been great. |
Here's the error. It's in "Karma Server" output:
|
@dminkovsky Try out the fix in the beta branch to confirm if it resolves the issue. You can use the vsix from the CI build, or build it yourself from the |
Released in v0.7.4 |
Describe the Bug
This tool expects
reporters
to be undefined or an array:karma-test-explorer/src/frameworks/karma/config/karma-configurator.ts
Line 114 in 7e3a9f6
However, contrary to the docs, Karma 6.3.16 accepts a single string value for
reporters
as well. Since my config was configured with a single string value, it would have saved me a lot of time if this tool also accepted single string values.Steps to Reproduce the Behavior
Use a string value for
reporters
. See that Karma works, but this tool fails due to the line above.Describe the Expected Behavior
This tool can accept single string reporter values, like Karma.
The text was updated successfully, but these errors were encountered: