In the Requirements Recap it mentions the from-Clause requiring at least 1 argument, but there are several test cases without any arguments, which is (apparently) supposed to be interpreted as an empty array as input.
I don't really understand how it's possible it broke. @dfhwze forked the kata a week ago, but that should have forked the fixed version. ( Eight years ago forking was not available - I probably just edited the kata directly, so there should be no wrong version to fork. )
The timeout issues you've experienced are because your algorithm is slow (most solutions finish in <= 1sec), otherwise yes I agree that the description could be more explicit about the desired shape of the cartesian products.
In the
Requirements Recap
it mentions thefrom
-Clause requiring at least 1 argument, but there are several test cases without any arguments, which is (apparently) supposed to be interpreted as an empty array as input.It also took me so long for such an easy solution. But I got it in the end!
I would ask you to please mind your language on the site. Also constructive feedback goes a long way further than just insults.
The shittiest Kata I've ever seen...
On input "from(...args)" I removed "name" index to be able to pass the tests.
from(...args){
if(args.length == 1){
args[0].slice("name");
There used to be a bug that when forking, you didn't always fork of the latest version. Perhaps that occured again here ..
thank you :)
no idea how it regressed either :(
Fixed again here - please ( review and ) approve.
I don't really understand how it's possible it broke.
@dfhwze
forked the kata a week ago, but that should have forked the fixed version. ( Eight years ago forking was not available - I probably just edited the kata directly, so there should be no wrong version to fork. )Resolved merge conflicts in description. I hope no earlier description updates got reverted. If so, let me know.
it's still happening, could you please fix it if you have editing / mender rights ? also,
chai.config.truncateThreshold= 0
is desperately needed ^^This comment is hidden because it contains spoiler information about the solution
The timeout issues you've experienced are because your algorithm is slow (most solutions finish in <= 1sec), otherwise yes I agree that the description could be more explicit about the desired shape of the cartesian products.
Make a Python version, begging u :(
Hint: dont waste your time on it
how stupid is this logic.
after 2 undo and 2 redo x should equal 50.
why it is not like this?
Loading more items...