yes, I was referring to the Solution tab. when you upgrade something, you usually want to leave that tab untouched, because it serves as a hint that no breaking change was made and previous solutions will still pass. of course there are exceptions if either:

• the solution was wrong
• the function's prototype was changed by the fork
• the solution was using deprecated features (either language-wise or Codewars-wise) and needs to be changed for forward compatibility

If you're referring to the Solution tab, no real reason. I just copied and pasted from my own solution. If that's not allowed, please let me know. For the refsol, I just tweaked it to use one loop instead of two and gave the variables better names. It's basically the same function.

why did you change the solution ?

Try it with a few small numbers on paper, and hopefully, you'll spot the pattern.

PHP fork to fix this issue and enable PHP 8.

JS fork:

• Enable node 18 (Mocha + Chai for assertion).
• Expand tests to fix this issue
• Edited description to fix this issue

JS tests fall short of the kata spec (0 < n < 10e6), and also found for n = 2441400 the reference solution returns undefined instead of the expected triplet, though it works for some larger values.

The triple chevron represents a Here String, which feeds the string on the right to the operation on the left(input redirection)

Shell fork for adding random tests. Fixes (partially) this issue

Although not explicitly stated, the sample tests indicate that the price isn't always an integer, so your calculation might be wrong, and also you type hint the input (see what happened when in not strict mode?).

Closing as this is not an issue with the tests.

Should be fixed by the fork above.

Approved by someone

PHP fork:

• fixing broken ref. solution.
• add input string to fail message

should fix this issue.

equal or greater.