Below you can see an excerpt from the description/sample tests in python, I replaced space characters by dots to make it easier to compare. The expected line length is 30 characters.

(1)"nunc,..at..aliquet.orci..Fusce"
(2)"at...dolor...sit...amet..felis"

The sequence of spaces in line (1) is: 2, 2, 2.
The word "at" at the beginning of line (2) could be appended at the end of line (1) if each sequence of 2 spaces would be replace by 1 space, couldn't it?

The order of expecetd and actual has been corrected wuth the above fork, but remaining points still stand.

https://www.codewars.com/kumite/67b90df78f99752cbe256030?sel=67b90df78f99752cbe256030
Kindly approve.

This one was fun.. but it is borked.

Starting from description (it is confusing) - and ending with tests:

1. It expects to not allow passing undefined values as arguments. I took that into account of course and added a throw... And the check in my code was done on every function call (as I believe it is reasonable that the deps objects may change on runtime). And.. it failed one of the tests. The correct approach was to not bother at all.

2. And secondly, it expects that arguments that are not present in the deps objects are... skipped. Completely ruining the order of arguments if some are not present, which makes this pretty useless approach even more useless.

And, of course, back when this kata was created - no such thing as default parameters existed, so it does not take them into account...

The haskell tests are totally broken; there are several solutions that just return a static string that succeed. Please fix!

This was fun, thank you!

Nice kata :)
But the specifics of the testing system do not allow it to be fully revealed.
There is now way to read incoming data from stdin, so there is no reason to write code for several Tb-lenght text ))
(Unless you desied to force yourself read input string byte-to-byte - sort of simulation reading from stdin)

fork here, it's roughly the same as the python one

really enjoyed this one.

@realitant test output has been changed so that it's no longer vague or asking you to comb through large lists for some unspecified problem. The description typo with string/line for a single word has also been fixed.

Approved.

Rewrite to reference solution comparison here: https://www.codewars.com/kumite/664f538ca2b677fe163387ed?sel=664f538ca2b677fe163387ed

note: contains description changes

If only one word fits on a line, it should be left-aligned and no trailing spaces have to be put after it.

The description somewhat assumes that you already have a rough idea how justify alignment works. Maybe I should try to reread it provided no prior knowledge.

Also the high number of issues comes from exceptionally bad assertion messages and the fact that the kata is old and was not fixed (and still is not in many languages) for 10 years.