You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jun 19, 2020. It is now read-only.
The code was incorrectly expecting that the resulting message to
send to the console was always set. It may not be if the caller
does not provide any parameter as in `logger.log()`
Same bug as in #32: the console appender also expected the final
bit to send to the console to be a string and not to be an object.
However, in browser environments, Woodman typically send objects
as-is to the console.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Woodman does not like it when the final message it is about to send to the
console
is empty. This happens when:woodman.load('console %message');
logger.log()
,logger.log(null)
orlogger.log('{}')
This should hardly ever occur in practice since it does not make a lot of sense to log nothing.
The text was updated successfully, but these errors were encountered: