can you show the log of the given arg.
Re-raised as an issue.
Why would you consider null or NaN to be numbers?
This kata doesnt make any sense to me.
This comment is hidden because it contains spoiler information about the solution
I have two issues with this Kata (Ruby version)
This is amazing 😂
The exception you are raising is probably something like "method retunr does not exist"
Nice typo - you were lucky 😉
Thanks for the feedback - I've updated exactly as you've suggested 👍
Test.assertEquals isReallyNaN(37), false
Test.assertEquals isReallyNaN('37'), false
Test.assertEquals isReallyNaN(NaN), true
Test.assertEquals isReallyNaN(undefined), false
Thanks for approving! My first published kata ✨
make a python version and I share a Python3 winding number solution
A Grammar file such as this one, used to generate a parser via a tool such as PegJS, is surely a winner on many fronts:
It is easier to:
It says "Beta Status:Testing & feedback needed". So you need more rankings and/or ratings. You have no open issues (or suggestions or questions, but I don't think they matter), otherwise the Beta Status might read "Waiting for issues to be resolved" or something.
There is no way to know who left the "Not satisfied" (or why, if they didn't raise an issue), but that isn't helping. I have read somewhere what the criteria for Ready to approve are, but I honestly can't remember where, or what they were exactly. You need ten ratings, but high honour users count multiple. And a number of rankings, same same.
I check if there are random tests and if those are not vulnerable to input modification, but I do that during beta already. Also if appropriate Test.asserts are used. All of those are not a problem with your kata. (Well, Test.expect(predicate===true) could just be Test.expect(predicate), and Test.expect(predicate===false) could just be Test.expect(!predicate). But functionally it's fine.)
Only thing to do I see is giving it more time.