Loading collection data...
Collections are a way for you to organize kata so that you can create your own training routines. Every collection you create is public and automatically sharable with other warriors. After you have added a few kata to a collection you and others can train on the kata contained within the collection.
Get started now by creating a new collection.
@ytorn I agree with you. From where I'm standing, there are only 3 few possible options:
Thank you all for taking the time to answer my question. @ytorn is correct, I can't use console.log() because of large size data. Just to clarify, I'm not receiving a timeout, the tests complete on time but the array Im returning is not equal to the expected one. I tried to login games, Rank, Team, For, etc but the only thing Im receiving is "expected [ Array(#) ] to deeply equal [ Array(#) ]". That's why I was wondering if maybe some good sould have a large dataset to test my code :)
My code has passed all of the sample tests but it is failing for the bigger ones. Could you please provide me any suggestions on what to look for? what kinda situations may not be present on the tests cases that are being tested on the bigger cases? By any chance, would you have any big test case that you could share with us? Thank you!
It will never stop amazing me how far I am of thinking about all of the many possibilities that Test Cases evaluate... It took me a while to figure this one out
@Blind4Basics I lost like 4 to 6 points (not exactly sure). Maybe I was downvoted somewhere as @GiacomoSorbi told me. I'll be paying attention to my honor metric and if somethig weird happens again I'll certanily open a report on the github repo. Thank you everyone!
My solution is working for about 80% of the test cases but fails for some of the "bigger boys" test cases. After analyzing a little bit further, it seems that my solution fails when it comes to strings with more than 150 characters which makes debugging extremly loooong! I usually use VS Code debugging with a NodeJS environment, and then Ill add variables to the watch section, breakpoints and stepping into the code parts Im interested in reviewing - Sadly this approach is not feasible for the test cases I'm failing.
Could you please provide me some tips on could I speed up the debugging a little bit? Maybe another approach?
Thank you guys, I didn't know that.
By ay chance, do you know if there is a way to drill down the causes of why my honor got downgraded?
Thank you!
I got scared at the beginning and lost some honor.... I came back and nailed it! Don't let this kata scare you by its name, it is totally doable.
This comment is hidden because it contains spoiler information about the solution