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.
It was pretty hard, and not very interesting kata as for me. Too much not obvious moments, and a lot of debugging.
Really nice kata to practice with.
whats wrong with this shhh
[['Johan Liebert', 'Gihren Zabi', 'Abelt Dessler', 'Drake Luft', 'Daisuke Aramaki'], ['Abelt Dessler', 'Daisuke Aramaki', 'Gihren Zabi', 'Drake Luft', 'Johan Liebert'], ['Drake Luft', 'Gihren Zabi', 'Daisuke Aramaki', 'Johan Liebert', 'Abelt Dessler'], ['Abelt Dessler', 'Johan Liebert', 'Gihren Zabi', 'Drake Luft', 'Daisuke Aramaki'], ['Johan Liebert', 'Daisuke Aramaki', 'Drake Luft', 'Abelt Dessler', 'Gihren Zabi'], ['Abelt Dessler', 'Johan Liebert', 'Gihren Zabi', 'Drake Luft', 'Daisuke Aramaki'], ['Daisuke Aramaki', 'Gihren Zabi', 'Johan Liebert', 'Abelt Dessler', 'Drake Luft']]
It should work for random inputs too: 'Abelt Dessler' should equal 'Johan Liebert'
why....
Your code does not consider person with 0 votes (i.e, not in the first element of each rows combined). They have the least votes and should be removed first, followed by those who have the least votes amongst the voted candidates. (Also, your code is trying to retrieve first element from an empty row that has been removed(ex: [[], ["abc"], ["a", "b"]]), resulting in
IndexError)Your code does not consider person with 0 votes (i.e, not in the first element of each rows combined). They have the least votes and should be removed first, followed by those who have the least votes amongst the voted candidates.
OP solved it, closing
Issue not with kata, user is accidentally returning
undefinedas an object key.Not a kata issue, user function is mutating the values used for generating error messages. Added protection against this for the future.
Always fix the tests, if a solution is invalidated by fixing the tests then it isn't a valid solution in the first place.
Still an issue with updated tests, but I have no idea why it is happening.
Does not appear to be a kata issue.
Resolved with update fork to Node 18
Does not appear to be a kata issue.
JS update to Node 18, chai + assert
Loading more items...