Great kata, looking foward to next series! I see you're likely using the hog-bait deck which is a sick one back then, but sadly CR now is just going downhill with all these changes especially the leaderboard calculation one ..... -_-

what in the javascript

Can someone pls share any link or explain how the hell .forEach handles this length properly and for() cycle not? )
Is it very important to understand in real life?

Fill it with 'undefined' according to new Array() length, it seems to be working in this case

🤯🤯🤯

Thanks for your help!

Currently the test assertion message is unhelpful:

expected {} to deeply equal {}

Consider better formatting like`expected [{[...expected].sort()}] to deeply equal [{[...actual].sort()}]`

Good point, going to think about it again!
Split the tests sir, thank you !

Should probably include more manual tests for varying scenarios:

e.g:

When it is impossible to figure out the entire current hand, solution could be padded with '?' or undefined values.

Also the current manual test case should be split up into separate tests:

it("should return empty list on empty input", ...);

and so on.

Just changed this approach, you just need to return as many cards as you can (but less than 5)

Fixed!

Just fixed the tests!

No problem, just making sure you capture it while it's unpublished.

Thank you, my bad, removed from publishing, working on it

Yeah, thank you, I should have checked tests better! Removed it from publishing for now