there is a bunch of additional checks run when you make an 'attempt' - at 'test' it just checks the expected functions have been used, but it doesn't check the retured table values are matching the criteria, it does it at the 'attempt'
The error messages still say descending instead of ascending... (Ruby)
This comment is hidden because it contains spoiler information about the solution
Yes, functional emoji is all that matters!
Besides that, he's Hacker 'Sakana'. Search for its meaning in Portuguese ('c' instead of 'k', for the sound) >_<
I added the 'can' while rewriting the kata specification which was ambiguous; I had read a comment which said that loops could be nested and my own solution was implementing this so I didnt know there were no actual tests. Too bad :(
Don't try to decypher description. Attempt and read the response of the tests, it's easier.
I liked this Kata, but i do have a fundamental question!
Is there any particular reason why you would use WITH over a simple join? What are the benefits?
I don't understand why, but my solution for the kata is passed all the test. When I click "Attempt" my solution is rejected by the system because of wrong values. What is the problem?
Honestly I didn't like how this question was worded. It made it very difficult for me to understand everything I needed to do.
It didn't pass because you forgot to add a semicolon at the end of your code?
You have to rename you statemets:
AS name and AS card_name
I don't understand, I literally unlocked the solution only to find out I had the same code as most people, yet it doesn't pass when I attempt?
What is the purpose of this kata?