With latest JS version, you can see every assertion as a standalone block, displaying the given input.
Very good and funny Kata! Thanks to author!!!
I think unit tests are wrong.
I think this report has not enough details to fix the tests.
I think C# unit tests are wrong
Added + reworked the testing code, it's now based on JS current testing code :)
Interesting challenge.
Should be fixed now
.
Python fork removing spacebars and Del symbols (with ASCII-codes = 32 and 127 respectively) from string generation. Yeah, the latter is actually looks like an empty char in CW =/
Del
Missing return type in initial solution setup of TS
Added fixed tests
Updated to Node v12
JS: No fixed tests
JS: Node v12 should be used along with its appropiate assertion tools (Mocha + Chai). Refer to this and this
Loading collection data...
With latest JS version, you can see every assertion as a standalone block, displaying the given input.
Very good and funny Kata! Thanks to author!!!
I think unit tests are wrong.
I think this report has not enough details to fix the tests.
I think C# unit tests are wrong
Added + reworked the testing code, it's now based on JS current testing code :)
Interesting challenge.
Should be fixed now
.
Python fork removing spacebars and
Del
symbols (with ASCII-codes = 32 and 127 respectively) from string generation. Yeah, the latter is actually looks like an empty char in CW =/Missing return type in initial solution setup of TS
Added fixed tests
Updated to Node v12
JS: No fixed tests
JS: Node v12 should be used along with its appropiate assertion tools (Mocha + Chai).
Refer to this and this
Loading more items...