Console capture does not log when message is falsy

Challenge Passing Values to Functions with Arguments has an issue. User Agent is: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/54.0.2840.99 Safari/537.36 OPR/41.0.2353.69.

Please describe how to reproduce this issue, and include links to screenshots if possible.

My code:

// Example
// Only change code below this line.

function functionWithArgs(c, d) {
 console.log(c + d); 
}
functionWithArgs(7,-7); // result is 'console.log never called '

Result should be 0, but is not. 

[systimotic]

What’s interesting to me is that most of the following challenges (global scope challenge and the local scope challenge) don’t verify the message at all, nor stringify it. The message “console.log was never called” is never shown because of the seed, so it’s a bit weird that it even exists. I think it would be a good idea to make sure it’s consistent for all challenges where it is used, if that’s possible.

[abhisekp]

Ah! Your hunch is right 😃 @erictleung This line https://github.com/FreeCodeCamp/FreeCodeCamp/blob/staging/seed/challenges/01-front-end-development-certification/basic-javascript.json#L2358 should read

logOutput = JSON.stringify(message).trim();",

The if statement is unnecessary.

When message == 0, it won’t output anything. 🙅‍♂️ according to https://github.com/FreeCodeCamp/FreeCodeCamp/blob/staging/seed/challenges/01-front-end-development-certification/basic-javascript.json#L2308