Thank you very much for your addition, I think it will be useful.

I'm sorry too. :/

In the future, before investing significant time, you might consider asking on Discord#help-author if kata ideas have been done before. There are some people with loong memories there .. ( and unfortunately a lot of things have been done before ).

Yes, they have a certain similarity, I'm very sorry. I will remove this kata. Thanks you very much.

Duplicate of https://www.codewars.com/kata/wave-sorting/

Please unpublish.

There is no way this kata will ever be 8kyu, so I don't see the point. It'll stay 7kyu regardless.

Thanks for your feedback. I think than prototype properties and Symbol as key is too much for 8 kyu. And here a number of simplifications were adopted for its solution.

I will add it to the description

• We don't have to check prototype properties;

fixed

fixed

fixed

fixed

Parent prototypes should not have enumerable keys. They can, but every JS programmer worth his salt knows not to extend prototypes enumerably.

If this were a 2 kyu kata, I'd agree. For the target audience, the lesson might be useful, but failing tests for it seems overdoing it, because the essence of this kata is not "if you're going to extend prototypes, do it correctly," it's getting enumerable properties on an object.

If this were a problem, Symbol properties might also be in scope for the kata. At the target level, I consider the simplifications acceptable.

I added it to description.

• Argument's strings (and object's keys) will always have one class in the string like 'button' and will not have more as 'button action'.

Even if you do, you still have to specify it won't happen. :/