Ad
  • Custom User Avatar

    so MoOse and moose would be treated the same way

    Test for "moose" expects false. Test for "moOse" expects false. Relevant assertions in tests are:

    assert.strictEqual( isIsogram("moose"), false );
    assert.strictEqual( isIsogram("moOse"), false, "same chars may not be same case" );
    

    Doesn't this mean they both behave the same way? What is different about them?

  • Custom User Avatar

    The tests expects false, I don't know what you're complaining about, the test is fine, you're wrong.

    assert.equal( isIsogram("moOse"), false, "same chars may not be same case" );
    

    That is the test, if it would be case-sensitive as you claim, it would expect true because o and O would be considered different letters, but it isn't.

  • Custom User Avatar

    Please reread what I wrote and re-check your tests. As many other users have pointed out, that test fails for them, as well. Case insensitization would mean that the case wouod be ignored, so MoOse and moose would be treated the same way. That isn't happening as it should be; it's not working as intended. Check your work.

  • Custom User Avatar

    Please read the definition of case insensitive here: https://en.wikipedia.org/wiki/Case_sensitivity

    In case-insensitive, uppercase and lowercase letters are the same, and that's what the test asks.

  • Custom User Avatar

    I would appreciate some explanation from you why you consider my answers wrong, and what is the error in tests you are complaining about, because I think I am missing something:

    • The word moose is not an isogram, because the letter o occurs twice.
    • The word mOose is not an isogram, because the letter o occurs twice, with differend case (lowercase and uppercase).

    The occurrence of letters should be done in a case-insensitive way, i.e. both lowercase letters and uppercase letters contribute to the count of occurrences. And this is how it works in JavaScript translation. So, what exactly you think is wrong?

  • Custom User Avatar

    There are absolutely ways to ignore casing here. Unfortunately, one of the tests written requires case sensitivity, so your function might be perfectly correct and still fail to clear this kata.

  • Custom User Avatar

    The instructions state that the function should be case INSENSITIVE, but one of the tests requires case sensitivity (i.e.: "MoOse === moose" // false;).

  • Custom User Avatar

    When I click attempt
    this test (UpperCaseAlphabetPlusOneChar) returns an error saying the expected result was False but it returned True, however when I try it in VS it returns false

  • Custom User Avatar

    Implement a function that determines whether a string that contains only letters...

    Clearly the above mentioned points contradict this point. Also description is shared amongst all languages, so changing the requirements of a specific language is not feasible, let alone the amount of languages and solves as of now ...

  • Custom User Avatar

    Fixed Julia, checked all languages as well, closing

  • Custom User Avatar

    Fixed

  • Custom User Avatar

    Forked and approved

  • Custom User Avatar

    Forked and approved C++

  • Default User Avatar

    hi, I've put the spoiler tag on your comment because anyone can see it, whether or not they have passed the kata. So: do not ever post code in this way

  • Default User Avatar

    This comment is hidden because it contains spoiler information about the solution

  • Loading more items...