-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
client.captureConsole isn't defaulted correctly if client config is defined #961
client.captureConsole isn't defaulted correctly if client config is defined #961
Comments
+1 Same issue although work around is to set it manually for now... issue I think pops up also in the grunt-runner Related |
Oh, thanks @gfxmonk! |
We should normalize this in config.js, check all the default values ( Sounds like an easy pull request ;-) |
This issue cost me a few wasted hours. What would be the right place to mention this workaround in the docs? |
The new client.captureConsole setting added in #850 (for #744) doesn't get defaulted correctly if you have any client options set. e.g:
In this case client.captureConsole is undefined, and you never see any console messages even though it's supposed to be
true
by default.This possibly affects all default arguments that are nested.
The text was updated successfully, but these errors were encountered: