Challenge Profile Lookup has an issue.
User Agent is: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/58.0.3029.110 Safari/537.36.
Please describe how to reproduce this issue, and include links to screenshots if possible.
My code:
//Setup
var contacts = [
{
"firstName": "Akira",
"lastName": "Laine",
"number": "0543236543",
"likes": ["Pizza", "Coding", "Brownie Points"]
},
{
"firstName": "Harry",
"lastName": "Potter",
"number": "0994372684",
"likes": ["Hogwarts", "Magic", "Hagrid"]
},
{
"firstName": "Sherlock",
"lastName": "Holmes",
"number": "0487345643",
"likes": ["Intriguing Cases", "Violin"]
},
{
"firstName": "Kristian",
"lastName": "Vos",
"number": "unknown",
"likes": ["Javascript", "Gaming", "Foxes"]
}
];
function lookUpProfile(firstName, prop){
// Only change code below this line
console.log(" Hello World ") // <--- This statement is not logged in the console window
// Only change code above this line
}
// Change these values to test your function
lookUpProfile("Akira", "likes");
there should be a way for a coder to check how control is flowing through my code. "console.log" statement is one such statement.
But console.log statement is not showing any output
Edit (@raisedadead):
Original code hidden here
Note: I think there is one more open issue for this same use case. That has to be tagged and attached to closing while addressing this.
Content Hidden - by mod
Hope this will helps in clsoing the issue.
Hi @rnallu Thanks, I have removed your comment because it provides coding assistance to the challenge. We strictly discourage that on this issue tracker.
This issue is about console.log not logging output to the console window on the page.
We need to filter and pipe the output this from the console.log being used in the browser debugger to the console window as well.
This done for other challenges.
@raisedadead , thanks but how can I get tot the thread related to issue above... please guide me to correct thread
Using return will print to the "console" under the instructions all the same.
I am assuming you want to see console.log out put on the webpage itself.
Not sure why would we want to override a native browser api and show it on the webpage.
Instead we can clearly see the console.log statements in browser's dev tools. I have tried that in atleast 4 challenges and it works for various test cases. Using developer tools is an integral part of web development and we should use that instead of hacking console.log to display on the web page.
Above all i see following comment on the very first challenge which says that console.log is going to be in the dev tools.

I suggest close it as by design.