You need to sign in or sign up before continuing.×
8 kyu
Hello Happy Codevarrior!
4,134 of 4,148ZozoFouchtra
Loading description...
Debugging
Object-oriented Programming
.avif)
This comment has been reported as {{ abuseKindText }}.
Show
This comment has been hidden. You can view it now .
This comment can not be viewed.
- |
- Reply
- Edit
- View Solution
- Expand 1 Reply Expand {{ comments?.length }} replies
- Collapse
- Spoiler
- Remove
- Remove comment & replies
- Report
{{ fetchSolutionsError }}
-
-
Your rendered github-flavored markdown will appear here.
-
Label this discussion...
-
No Label
Keep the comment unlabeled if none of the below applies.
-
Issue
Use the issue label when reporting problems with the kata.
Be sure to explain the problem clearly and include the steps to reproduce. -
Suggestion
Use the suggestion label if you have feedback on how this kata can be improved.
-
Question
Use the question label if you have questions and/or need help solving the kata.
Don't forget to mention the language you're using, and mark as having spoiler if you include your solution.
-
No Label
- Cancel
Commenting is not allowed on this discussion
You cannot view this solution
There is no solution to show
Please sign in or sign up to leave a comment.
A good kata but it's a not 8ky
A good kata with a little bit confusing description. A hint: fix the EXISTING code.
Fixed formatting a little bit because of crappy initial code and it passed all of the tests... What? Why is it even a task? This kata should be retired for good.
Thanks for the Kata!)
Please, can one of the contributors add the tag
OBJECT-ORIENTED PROGRAMMING, as the task includes OOP functionality?)done
This comment has been hidden.
i try to fix it with const it did not work and i dont know why?
Hint: boris.name("boris") should also return "boris"
JS :
Changed.
I think this Kata needs a bit more explanation on the instructions, or to be 7th kyu... As a JavaScripter with little OOP experience it took me a long while to get it, and I'm still not super sure why it works the way it works... The lack of description about what is going on with the tests is quite frustrating. BUT this is an awesome topic that I wish I knew more about and Im glad I got this kata.
Any chance you could point me in the right direction?
Lacking random tests, should include random tests for resetting warrior name using
this.name.I am not sure that random tests are so critical in very low level kata, especially bug fix ones. Anyone who could hard code this is likely to not be learning from the bug-fixing anyway.
That being said, a couple of random tokens were added.
this was supposed to be easy?!?
This comment has been hidden.
"name is not defined" means, quite unsurprisingly, that
nameis not defined.this.nameis.Also, you are using
this.nameas a function in yourtoStringfunction. Why are you doing that?This comment has been hidden.
This comment has been hidden.
This comment has been hidden.
This comment has been hidden.
This comment has been hidden.
It's because you are printing albert's value before you make boris. Try printing albert's value after you have defined boris and you'll see something different.
Aha yes, it prints
Hi! my name's Boris twice but doesn't print Albert at all...
This comment has been hidden.
This comment has been hidden.
Cracked it in the end! It looked so much more complex than it actually was!
Can someone help me with understanding this line? I thought when you declare an if statement, the conditions need to be all within the brackets?
This comment has been hidden.
This comment has been hidden.
This comment has been hidden.
This comment has been hidden.
Fixed it
Congrats Happy New Warrior !
Instructions are not clear.
There's a bug in the
Warriorclass (the kata is taggedBugs). You have to fix the bug.