Testing Objects for Properties needs clarification.

Challenge Testing Objects for Properties 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. Please describe how to reproduce this issue, and include links to screenshots if possible.

My code:

// Setup
var myObj = {
  gift: "pony",
  pet: "kitten",
  bed: "sleigh"
};

function checkObj(checkProp) {
 if(myObj.hasOwnProperty(checkProp)){
   return myObj[checkProp];
 }
  return "Not Found";
}

// Test your code by modifying these values
checkObj("gift");

edited by mod

Issue Description

Clarity issue on this problem - User allowed to use dot operator to access value. however using dot operator(obj.prop NOT obj.“prop” as given in the paramater) in this instance creates undefined value - out of scope of this exercise

[Manisha11sep]

Hi @mszaf @rdsandovalm my code is working find for all the values. var myObj = { gift: “pony”, pet: “kitten”, bed: “sleigh” };

function checkObj(checkProp) { // Your Code Here if (myObj.hasOwnProperty(checkProp)){ return myObj[checkProp]; } else{ return “Not Found”; } }

// Test your code by modifying these values checkObj(“pet”);

Its really weird that its showing error for using .operator instead of [] while accessing the values of myObj. I searched online and everywhere it saying we can access property of a object in two ways:-

1. ObjectName[“propertyName”]
2. ObjectName.propertyName I hope it will help.

[systimotic]

Hi @mszaf! Thank you for reporting this issue.

It took me a bit to understand what you were saying, so to save others the same struggle, here’s what I believe this is about. This challenge does not mention how to return the value when it is present. Campers could try to return the value as return myObj.checkProp rather than return myObj[checkProp] The previous challenge talks about the correct method, so I feel this is probably fine as it is.

What do you all think?