Translation solution in *actual* author's name about codewars.com HOT 4 OPEN

This would be good for forking in an existing language as well. The author's solution does not always pass the tests anymore, but a new example solution is still published under the original author's name. If a modified example solution is published, it should be published under the fork author's name.

from codewars.com.

One complication that just occurred to me is that if a modified solution were to be credited to the forking user, then that would mean on an as-of-yet unapproved translation, the original author of that translation would no longer have a published solution. In effect, it would rob them of a solved kata and they might never know about it.

What we'd need is effectively a tree of solutions that are all published once the translation is published (if the original solution was modified before approval). Any latest solution of a unique contributor in the tree that passes the approved fork's tests is then submitted as a solution.

One might argue that someone could just fork an unapproved translation, make a tiny trivial change to the solution, and publish for approval, thereby guaranteeing an automatic "solved" status in the kata despite not having actually written their own solution. But I guess this would be a rare case and could be handles like any cheater is handled.

from codewars.com.

Any solutions that pass the tests can be submitted as a valid solution. Any that do not can be published as invalidated. Invalidated solution still count as solved.

Translations still have to be approved. If it's a fork with a trivial change in the solution, this will be visible to the approver.

from codewars.com.

If it's a fork with a trivial change in the solution, this will be visible to the approver.

Only if the reviewer bothers to inspect the diff of a fork closely. I can't speak for others, but I often don't bother analysing the example solution beyond the fact that it passes the tests, but I ensure the tests are correct.

from codewars.com.