I'm not enough of an expert to answer your question, but would like to mention that it is possible (though not necessarily better) to solve this without using switch or if statements.
I would like to second Blind4Basics' comment and suggestion. I think that including an import for Collectors would be giving a bit too much of a nod towards the solution and is unnecessary, but for things that are in the definition of the problem like Map and List, it could add to some begginner frustration if they don't recognize the missing imports and run their code potentially multiple times with minor errors like that in there.
But this has been a very useful introduction to using Streams that's made me comb through the documentation, thank you for that!
I think I corrected this now. But some solutions still show up as invalid, even though I tried to copy-paste them and they actually work fine with new test cases. Could be some CW glitch.
EDIT: All good by now, all valid solutions with old names are valid again.
Oh, another thing: I am not sure if once listed as invalida the old solutions may be checked again or not, but uers will keep their points and still see this kata as solved despite the function name change, so it is really a minor issue: don't worry :)!
Done, now it should work (wait some time if older solutions are still listed in red.
Feel free to do a test run on the updated kata, now sporting a good deal of random test cases with my usual pop culture references (this time from the main characters of "The Oz").
Giacomo can you plz check the test case cause i made a mess by changing the function name , and because of that all the solutions that were already made becomes invalid so can you fix it and just send me the whole fixed test case - For Javascript
You changed it to a wrong name. should be 'nameShuffle' or 'nameShuffler'. As far as I know, there is no word 'suffle' or 'suffler' in English.
Also, when you change the main function name, consider adding support for the old name as well, because otherwise all old solutions become invalid. To do provide back-compatibility, just add a line like this to the test cases:
🦊
I'm not enough of an expert to answer your question, but would like to mention that it is possible (though not necessarily better) to solve this without using switch or if statements.
I would like to second Blind4Basics' comment and suggestion. I think that including an import for
Collectors
would be giving a bit too much of a nod towards the solution and is unnecessary, but for things that are in the definition of the problem likeMap
andList
, it could add to some begginner frustration if they don't recognize the missing imports and run their code potentially multiple times with minor errors like that in there.But this has been a very useful introduction to using Streams that's made me comb through the documentation, thank you for that!
I think I corrected this now. But some solutions still show up as invalid, even though I tried to copy-paste them and they actually work fine with new test cases. Could be some CW glitch.
EDIT: All good by now, all valid solutions with old names are valid again.
Oh, another thing: I am not sure if once listed as invalida the old solutions may be checked again or not, but uers will keep their points and still see this kata as solved despite the function name change, so it is really a minor issue: don't worry :)!
Done, now it should work (wait some time if older solutions are still listed in red.
Feel free to do a test run on the updated kata, now sporting a good deal of random test cases with my usual pop culture references (this time from the main characters of "The Oz").
Ok
If you are ok with it, I'll do the work that MMMAAANNN suggests :)
Giacomo can you plz check the test case cause i made a mess by changing the function name , and because of that all the solutions that were already made becomes invalid so can you fix it and just send me the whole fixed test case - For Javascript
I approved
No luck approving even the forked Ruby translation?
can you gimme the whole test case :)
ok change it
I see the usual annoying bug; try approving the forked version (the most recent one) now, if you don't mind.
Than are you ok if I change it all to "shuffle"?
You changed it to a wrong name. should be 'nameShuffle' or 'nameShuffler'. As far as I know, there is no word 'suffle' or 'suffler' in English.
Also, when you change the main function name, consider adding support for the old name as well, because otherwise all old solutions become invalid. To do provide back-compatibility, just add a line like this to the test cases:
Loading more items...