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.
Unpack returns an array, and * is just a shorthand method to join the array as a string by the supplied delimiter ('.')
Typo in description. "Write a
bdy
"Stupid and worthless cata.
Wow! Could you explain please how * works in your solution?
Wow, very elegant!
This kata has very unclear description... For what sake do you need key_1 and key_2? oO
Thank you. Another bite of JS to know.
I've opened the Catalog and filtered it by:
It displays a number of katas.
So:
Thank you.
Ah. Yes this is a JavaScript issue. In Ruby
[1,2] == [1,2]
will be true, but in JavaScript it will be false because they are actually two different memory objects/references. IMO, ideally in JS[1,2] == [1,2]
would be true and[1,2] === [1,2]
would be false - but this is not the case.Because of this we provide the
Test.assertSimilar([1,2], [1,2])
method which will return true.One caveat to be aware of is that this method can be used to assert similarity of two objects (such as
{a: 1, b: 2}
but it enforces key order. SoTest.assertSimilar({a: 1, b: 2}, {b: 2, a: 1})
would be false where asTest.assertSimilar({a: 1, b: 2}, {a: 1, b: 2})
would be true. In the next version of the framework we are going to fix this.Ah. There are less fundamental kata than there are algorithms. Plus it looks like you are focusing on Ruby and CoffeeScript which have less than JavaScript. We start giving you old ones once you have gone exhausted the list. Does this sound about right or is this happening for JS kata as well?
Also retraining on kata isn't such a bad idea. In fact thats part of what kata are all about. Try exploring new ways of solving old problems. You can always look at your previous solutions and see if you can improve upon them further.
Fundamentals.
Test.assertEquals([1,2,3], [1,2,3])
What is the test case that you are running?
This should have been fixed a few days ago. Is this still happening?
That shouldn't be happening. Which "focus" are you using? "Fundamentals" or "Rank Up"?
Loading more items...