I approved but I realize afterward that random tests should be shuffled. testShouldWorkForRandomNumbers almost never generate squares.

new fork to resolve merge conflict

https://www.codewars.com/kumite/5d865611035485001cd87085?sel=5d90badfb670170023b14760

(it'll need another week)

Merge conflict.

https://www.codewars.com/kumite/57a6651fe298a7336400060a?sel=5d865611035485001cd87085

The description has been updated, so new tests should be added:

0 <= input.length <= 100
Along with opening (() and closing ()) parenthesis, input may contain any valid ASCII characters. Furthermore, the input string may be empty and/or not contain any parentheses at all.

The description has been updated, so new tests should be added:

0 <= input.length <= 100
Along with opening (() and closing ()) parenthesis, input may contain any valid ASCII characters. Furthermore, the input string may be empty and/or not contain any parentheses at all.

And how about random tests?

testShouldWorkForRandomNumbers
Error: Call to undefined function assertEquals()

"Your answer was wrong for " + $r - + is numeric addition.
solution is available in solutions and has a trivial name.

Good catch. I fixed and added test cases for "90, 180" and "-90, -180".

Nice work!

Just note that 90,180 are valid coordinates. You should use > and < instead of <= and >= in your solution.

agreed.

p.s. my bad I didn't know tagging as issue would have any other consequences

This is maybe a suggestion, but not an issue.
Cause of the issue it is not possible to approve this kata.

Please close this issue!

I think it would make it slightly more interesting to require different characters inside the triangle vs outside (e.g. spaces inside vs underscores outside)