The kata tells you to create a solution but it is more of a bugfix in this case. Change the descrpition or the preloaded solution to make the description consistent.
Spacing in first solution is inconsistent, making it hard to read https://github.com/airbnb/javascript#whitespace
Anyway. That's not the point. This kata doesn't have to use loops because it's solvable through sorting. Maybe you should drop initial code entirely, and leave only function declaration?
It would be great if we could get more instruction on the specific features on the beta site. Also, a way to fork current questions to modify and re-publish could be a great way to help new posters.
The kata tells you to create a solution but it is more of a bugfix in this case. Change the descrpition or the preloaded solution to make the description consistent.
Spacing in first solution is inconsistent, making it hard to read
https://github.com/airbnb/javascript#whitespace
Anyway. That's not the point. This kata doesn't have to use loops because it's solvable through sorting. Maybe you should drop initial code entirely, and leave only function declaration?
More test cases should be provided
Test.expect-Test.assertEqualsgives much better debug outputIt would be great if we could get more instruction on the specific features on the beta site. Also, a way to fork current questions to modify and re-publish could be a great way to help new posters.