Closed SantoJambit closed 4 years ago
@SantoJambit , are you OK with the usage of console.debug(error)
instead?
@Yaffle that doesn't change anything for the better.
In our code-base we use loglevel to prevent such informations from leaking where they should not be, but I don't think one console statement is worth introducing a new dependency in this case.
@SantoJambit , right, what about console.debug("TextDecoder does not support streaming option. Using polyfill instead: " + e.toString())
?
@Yaffle yes, that would be good.
@Yaffle when can we expect a release?
@SantoJambit , just released, thanks for the reminder
Currently, there is a log output, which prints a full stack trace whenever the TextDecoder polyfill is being used.
Would it be acceptable to change this to a one-liner
"TextDecoder does not support streaming option. Using polyfill instead."
or even suppress the message altogether?Otherwise I'm getting spammed with stacktraces during my test-runs, which makes the log pretty hard to read.
Aside from that, we would like to not have errors in the console unless they actually cause invalid behaviour.