I'm not sure y this one got approved, but it looks very similar to this (I'm also not sure why I did not think about this kata being a dup back then, && even gave it a green vote ughhh...... )

Trivial map/filter/reduce is not a novel kata idea.

You don't mention anything about case sensitivity.

It is a duplicate of the kata you mentioned in the description.

It's not stated how to format the result when the input has 4/7/8/9/10 digits.

Don't close issues without fixing them.

Incomplete Testing

Conditions: May be any length. (up to MAX_SAFE_INTEGER)

This statement doesn't make any sense. Integers don't have length per se (unless we assume that "number of digits = length of an integer" in some specific base), and obviously a number cannot have 9 quadrillion digits.

Also, the input type still hasn't been changed to a string.

The link to the retired kata should be removed

Testing is not thorough enough; for example.

API's, that could help directly formate numbers, are disabled.

This makes no sense whatsoever, and it isn't tested (and, frankly speaking, should be dropped entirely).

JS and TS: the initial solution should not return the number in string format, instead it should just return nothing or ""

• Python function name should use snake_case

• Now the python version does not only contradict with the description, but with other languages as well.

45932
'+459  32' should equal '+ 459 324 59 32'

7020089369
'7020089369' should equal '+7 020 089 369'

You should stop translating to other languages before current issues are fixed

A bigger issue at hand: JS/TS language versions have a completely different (even with different specs) test fixture compared to the Python version ;-)

Please note that you do need to make sure test fixture stays consistent across language versions.

JS: random tests are not run at all because the test blocks are not nested correctly.

Note that only the most inner test block (that contains test assertions) should be it; every parent block should be describe instead.

The description doesn't actually explain the task at all, and instead creates more questions. Why is there suddenly a + sign and we have to return without it? What even is should return "## ## ##"? (Clearly we're not returning a string with #s here.) What even are distinguishable country/zone/client codes?

And the examples are just as unclear while the sample tests only contains one particular kind of test cases. It's all very bad.