• Same. Cannot solve this.

  • This comment is hidden because it contains spoiler information about the solution

  • I have the same issue.

  • Time: 617ms Passed: 5 Failed: 0 Exit Code: 7
    timers.js:817
    this.domain = process.domain;
    ^
    ReferenceError: process is not defined

    what could be wrong? tests all passed

  • This comment is hidden because it contains spoiler information about the solution

  • I would recommend denoting this to 7 kyu.
    Just solved a couple of 8 kyus that were much harder.

  • Good suggestion. I'll fix that up.

  • Nice Kata. In addition to getSecret() and setSecret I also had a secret property. The error message I got was:
    "no property called 'secret'"
    It took me way to long to figure out I just needed to remove the secret property.

    I feel something like:
    "There should be no secret property"
    would be much more effective.

  • what is happening here?

    ReferenceError: console is not defined

    the submit test is trying to run console.log, which is not working.

  • I'm getting the same thing right now

  • This comment is hidden because it contains spoiler information about the solution

  • The only way I've found to find a user is if you already know his or her username. Then you can go to www.codewars.com/users/[username]. Also, if someone has signed up using your referral link, his or her username shows up in your profile under Earn extra honor, invite code warriors!. Click Learn more.

  • Yeah, something like that. Don't let the user directly get or set the value; just let them influence it, or influence what comes out the other end.

  • Ah, you mean because I make a setSecret() and getSecret() it doesn't demonstrate the value (if you have a setter and getter why not just have a property? Would you find the kata more interesting if getSecret() did something besides return the secret, like masked part of the secret (thinking about SSN's or something)?

    I'll ponder a way to make it a more interesting application to demonstrate value. Good feedback.

  • Yeah... I think my problem is that you say "There's no such thing as private properties". But the "secret" variable here is effectively completely public anyway, making any secrecy or closure completely superfluous.

  • Loading more items...