Chrono79 Just because the final solution is easy doesn't mean the process to figure it out is easy as well. It requires low effort to draw a complex maze with thousand of crossroads, then make the exit with a straight line from the entrance. Staying at the exit, the path is clear, staying at the entrance it isn't.
I was wondering that myself, it seems like it isn't ranked properly if that's the case.
The kata is based on a trick more so then actual programming, which seems to defeat the point of a code kata.
That's strange, it validates for me, and it looks like every Test.it() is correctly nested in a Test.Describe.
Does the error say if it's failing for you on the Random Tests or on the "Returns correct boss orders" tests?
Indeed
That's the reason there is a warning in red, the
PUZZLEtag, and the following line in the description:I'm not gonna argue about it, tho, you can have your opinion, I keep mine.
Chrono79 Just because the final solution is easy doesn't mean the process to figure it out is easy as well. It requires low effort to draw a complex maze with thousand of crossroads, then make the exit with a straight line from the entrance. Staying at the exit, the path is clear, staying at the entrance it isn't.
@C_Minor So you assume the wheel, as it was first invented by a man named Dunlop, is the best iteration of the wheel?
it's an ancient JediScript mind-trick
I was wondering that myself, it seems like it isn't ranked properly if that's the case.
The kata is based on a trick more so then actual programming, which seems to defeat the point of a code kata.
Ты душный, братик... Может ты банчишь мороженым на москварике?
It has nothing to do with having to write everything from scratch.
This comment is hidden because it contains spoiler information about the solution
This isnt cheating imo, he went out and found a bignum. Then used it in the code he wrote. Are we supposed to rewrite every library function we use?
No need to be bitter, johnahnz0rs.
because it's a stupid kata submitted by a loser.
Because the solution is easy.
Ah, my bad. Looks like the example test case wasn't wrapped in a describe. It should work now.
That's strange, it validates for me, and it looks like every Test.it() is correctly nested in a Test.Describe.
Does the error say if it's failing for you on the Random Tests or on the "Returns correct boss orders" tests?