😂

Languages with parameter type declarations are given buggy starter code. Either the description should state that the user is expected to fix the code for those languages, or the starter code should be correct from the start.

EDIT: Actually, it seems that it's just typescript and potentially scala that have this issue. In light of this, I think these languages should have correct starter code like java and c#.

That's fair, I don't think it's great that the kata gives you buggy code and makes no mention of it in the description.

Thanks for the response. I was pretty irritated, but leanred something here. I still don't think this was a great kata...at least when comparing it to literally every other kata I completed.

It is kind of sneaky for an 8-kyu kata to do that, but there is nothing preventing you from changing the function signature. You are allowed to edit all of the code in your solution.

Unpublished.

This kata is a candidate for removal. Please vote here to help us get rid of poor quality kata, or tell us how to fix them: https://github.com/codewars/content-issues/issues/232

TL;DR

I think I will just ask about retirement of this kata. There might be some idea behind it initially, but over time, it took way too many wrong turns. Totday it's a mashup of requirements literally translated from Java into languages where they are unidiomatic, and quite often untestable.

There is too much to fix here, and getting rid of this challenge will be a much cleaner solution.

idk whose fault it is or anything, but this is the first time I look at this kata and it doesn't present itself well at all in python

right off the bat it's lying about how it is called

Solution.main("parameter1", "parameter2", "parametern")

when it's actually a varying number of parameters and why are there even parameters to begin with

and the sample tests do a very poor job of showing how the code gets used which is especially bad given what the initial code looks like and how the solver in general is not told what the interface is

the oldest translation has this as the ENTIRE description:

For this Kata you should write a program in main mode that prints the phrase Hello World! to the console's standard output.

no function/method arguments. .. somehow it all derailed and become something completely different, and weird and with nobody being responsible for it making sense.

and there's a class. it.. doesn't say why there's a class. description says I'm given a method main. I'm not given such an argument or pre-existing code or.. any interpretation of that. and the class seemingly has no purpose. kata's author wanted a class to be used because obviously everyone should write java in their python, regardless of language semantics.

it also reads like there's some sort of gotcha in there. it reads like it should have puzzle tag. except no. no catch. stock standard hello world. one call to print. except it all went wrong.

original language being java, it shows how it is executed from commandline. but the python one doesn't. that seems like a very strange translation choice.

am I being a dummy? am I missing something?

The instructions are extremely vague. I have no idea what the test is expecting me to output except for some kind of print() statement, that is of course not working, because the instructions don't really explain what more is needed than a print statement.

fixed

merged new fork