Approving kata should not be possible when users' solution is obsoleted

[dinglemouse2250]

Sometimes a user passes a Kata when it is in "Beta".

Later the Kata is modified, and so that solution become invalid.

Yet, for some reason the CW check for "ability to approve" seems to test only that the user has solved the Kata, but it is not requiring that their solution is still valid.

And so a broken Kata can be approved without the approver even aware it is broken ...

┆Issue is synchronized with this Clickup by Unito

[Voileexperiments]

The solution to general problems like this is, clearly, fix it quickly. That's why CW is community-based, and the strength of being able to be agile. In fact, currently the only thing that can't be done is to revert duplicates that have been approved (there are a few of them), and this is the thing that should be fixed.

As for the kata you're probably referring to, I've made a comment there which outlines the thought.

Also, I once have replied to JohanWiltink on another CW kata some time before, but bureaucratic solutions will not work on this because CW's nature is incompatible with bureaucracy. Rather than making beta katas harder to be approved (which gives pain to everyone involved in the process), I'd much more like the ability to send back a recently approved kata to beta.

[CliffStamp]

I am not sure that would be a good idea. It would require someone to complete the kata any time their solution is invalidated, but that happens often for trivial reasons. Plus once you have solved a kata all of the solutions are open to you, even the new ones so what is the point?