"a date from the 20th century." ;)
ofc you can...
Considering the current satisfaction rate of your kata, the chances it can go out of beta one day are pretty close to 0. Moreover, in one month, you haven't tried to resolve the issues below (random tests + new test framework), meaning you obviously don't care about it. So it will be pushed back to draft again, for all those reasons (and the fact that the task ins't interesting and we already have a lot of kata based on the very same principle) and you really should leave it there at the very least until you resolve the issues mentionned above. But I'd advise you to just keep it in your draft section, because as I said before, it has close to no chances to get approved one day anyway.
Your kata is currently not describing the actual task. That's not acceptable.
I changed the description
yeah, that's why 3 are grouped and 3 others are in another group. How convenient... (edit: well, 3 others aren't grouped, but it's the exact same code, with the same var names, it's just more or less deployed)
description hasn't been changed, don't resolve issues like that.
@dfhwze: warning, don't raise issues about that. It's better if it's there, but it's not mandatory (otherwise, you can raise this on the whole database)
Closing as an issue, but valid as a suggestion.
We made up our own solutions ourselves and I didn't share the solutions with them
on a failed test we get for instance:
10011000 should equal 1100010
but the input string is not in the assertion message
What do you mean?
the task still isn't described properly.
Side note: those of your clan, stop to upvote each others (more precisely your kata) while you all have the same solution...
Moreover, Latin does not distinguish between i and j characters (actually j is a late creation in Romances languages)
\o/ (at last...)