So is this issue.

This issue was already raised below.

Failing tests isn't an issue, though this author never responding to anything certainly is.

That isn't a kata issue, it could simple be a code issue.

Not an issue.

For this to be an issue, specific references are needed, otherwise it is impossible to know if it was fixed.

.

And so is this issue.

Needs more test cases. Not checking for some edge cases which means some non-Arrays are being identified as Arrays.

Major issue: This kata is a duplicate of the "Array.isArray" kata.

http://www.codewars.com/kata/525a4cab1650d76b8000084d

The issue and solution is the same for both, although the existing kata seems to give a better hint as to why the test fails in the case where __proto__ or the constructor property is used.

So: I solved this via copy and paste.

I am not opposed to duplicating existing kata, if there is a substantial twist or at least something original to give it added value. There's not much additional here so far, other than a few test cases being put into the description as examples. For me that's not enough to justify making another kata out of it.

Is there any chance to debug this kata? I mean to see console.log of input? Because now it shows "Maximum call stack size exceeded"
Also - can somebody explain me please, what do that mean "Don't forget that array.proto should be link to Array.prototype" ?

Can't debug due to "RangeError: Maximum call stack size exceeded"

It's not for beginners, esp the last test's desc isn't clear at all

i'm too :( what's happen?