Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
Seems like it’s reinventing the natively-provided wheel, doesn’t it? Is it really worth extra framework weight? Why do those frameworks feel the need to define it as an additional feature when for...in seems to serve the feature’s purpose just fine?
for ... inalso catches properties down the prototype chain. You have to use the.hasOwnProperty()method to filter things out.