Ad
  • Default User Avatar

    please do not open issues when you are asking for help.

  • Default User Avatar

    The answer was three. Finally just reworked my code to test random things and it passes now. Nowhere was it explained that a three or more way tie for gold means NO OTHER medals are awarded whatsoever. Would be good to add that!

  • Default User Avatar

    HOW MANY PEOPLE CAN TIE FOR GOLD BEFORE NO BRONZE MEDAL IS AWARDED?
    ANYONE??

  • Default User Avatar

    @Blind4Basics Can you please explain the conditions under which there can be multiple medal winners and when a medal is NOT awarded in that case? I'm stuck unable to pass the random tests because it seems to confusingly fail, saying that there should not be Bronze winners because there are multiple Gold winners,despite this being perfectly acceptible in Example 3. Whatever the rule is here, it is not explained, and I'm stuck on this kata until it is made clear.
    Thank you!

  • Custom User Avatar

    Typos:

    In each round, players can score(d) positive or negative points (between -100 and 100).

    If by misfortune, there is noone (-> no one) on the podium.

    'Sandra': [], // Sandra is declared a forfeit (-> shall be declared forfeited)

  • Custom User Avatar

    done

  • Custom User Avatar

    should be fixed with alphabetic ascii characters names used

  • Default User Avatar
  • Custom User Avatar

    @ostaladaFab: just remove all special chars. It's the simplest way out of this.

  • Custom User Avatar

    almost good about the general structure: you need to choose randomly between the different kinds of generators. For now, the kind of output isn't random. ;)

  • Custom User Avatar

    Maybe it was wrong of me to assume that it should be sorted lexicographically (?) and not by ordinal values. Just by the way it sounds it looks wrong, if we operate in english. I have no knowledge in that field, so I wouldn't claim to know anything. Here's some interesting examples that I based my assumption on:

    console.log('a'.localeCompare('ä', 'en'))  // -1. a < ä
    console.log('b'.localeCompare('ä', 'en'))  //  1. b > ä
    console.log('a'.localeCompare('ä', 'en', {sensitivity: 'base'}))  // 0
    

    Whatever the case, the expected sorting order is not defined in description, so that's an issue.

  • Custom User Avatar

    Because it produces results which can be considered wrong (or, at least, unexpected), and if locale-unaware sorting is required, it shoud be specified in the description.

  • Custom User Avatar

    Why not sort without using localeCompare?(Q =(a,b)=>a>b?1:b>a?-1:0)

  • Custom User Avatar

    Like B1ts said, sorting language sensitive information (and peoples names can be considered such) by ordinal is... not good. In Polish, correct sorted order is ["bak", "bąk", "byk"], and if you sort it by ordinal, you get wrong result.

  • Custom User Avatar

    the expected order is incorrect

    How?
    BTW:

    >>> ord('é')
    233
    >>> ord('o')
    111
    
  • Loading more items...