Loading collection data...
Collections are a way for you to organize kata so that you can create your own training routines. Every collection you create is public and automatically sharable with other warriors. After you have added a few kata to a collection you and others can train on the kata contained within the collection.
Get started now by creating a new collection.
Issue unclear. Resolving.
Also, 106 people have completed the kata already, so the description is fine.
Guys, thank you for task, but the description, cant understand it, did code in my way as understand.
Added random tests in python.
Re-raised as an issue.
Yes. Unfortunately, the author does not pay attention to wording the description. However, I appreciate the work put into these kata exercises.
Description should be language-agnostic (e.g. Python desc. should not be written in camelcase).
It's been a while so you've probably learned this, but you can change the tests.
Thanks for double checking. @Hobovsky just approved the translation!
The description diff is correct. The description was made language agnostic removing all these language-specific blocks and this translation now has the current shared state of the description.
Thank you for submitting a fix for the broken "Kata example twist" Swift tests.
The good news is it looks like you fixed the horribly broken tests.
The bad news is (based on the diffs) I'm concerned about the integrity of the Description, which is shared amongst all the languages. I've asked a moderator to take a close look at it. The diff is confusing when I look at it.
For reference, here's how to add swift-specific lines:
One other minor nitpick is to get rid of the sample comments //TODO at the top.
yeah, the same thing happened in MULTIPLE renditions, especially in JavaScript. I lost track of how many coders had something like that in their preloaded but didn't have a clue it was there when they published, lol
haha, also the possibly misleading intentional misspelling of the class
The fact that the definition of
class _()stayed in that forked code is quite funny.It's also showing how hard it can be to maintain a good architecture even for simple code, because when you are not the one that made the code, you don't know the location of every piece of code, and you easily forget to remove some.
I really stared at that one for a minute before searching for the additionnal preloaded code !
So funny solution...
Loading more items...