Kata was auto-retired due to low satisfaction rating.

handling inconsistent input types is.

Correct, it was my main goal to create a kata for handle different type

Filtering seems not to be the ( intended ) essence of the kata, handling inconsistent input types is. That also has been done, but the combination is not entirely hopeless.

You should really have had decent random tests before you hit Publish. Not having them is unforgivable and reason enough to downvote for a lot of people; now you'll never know if they didn't like the concept or the execution ( or possibly both ).

If there are multiple issues like this, I encourage you to raise them in seperate issues so that the auto-unpublish feature kicks in

Random tests should have unpredictable outputs, not just unpredictable inputs. Removing exactly the first and last element is too predictable.

I'm not sure I can link you an exact duplicate, but I consider your kata a duplicate of any basic filtering kata.

I will add [UPD] I have added random test

It is recommended to have more than 1 random test. I really recommend you read the entire guidelines section.

You can muddle the input format even more by requiring accepting removeFriends(friendsList, 2, 3); // remove Bob and Charlie. It's even possible to pass in a list element to be deleted ( won't work with a literal, but will work with the actual object ).

Personally I like strong, static typing, so I'd just hate that even more, but it would fit with the theme.

Hi, I generelly try to search any polymorphism / typeof task where u, for example, can get number vs string, or single number vs array of number - but I don't find anything. Can u show me example of this tasks?

And about random test, sure, I will add
[UPD] I have added random test

Hi,

• No random tests
• Duplicate and/or not novel idea

If you're interested in authoring kata, you should follow the existing guidelines for doing so.