6 kyu
I'm longer than you!
377 of 848Pixie11
Loading description...
Strings
Fundamentals
View
This comment has been reported as {{ abuseKindText }}.
Show
This comment has been hidden. You can view it now .
This comment can not be viewed.
- |
- Reply
- Edit
- View Solution
- Expand 1 Reply Expand {{ comments?.length }} replies
- Collapse
- Spoiler
- Remove
- Remove comment & replies
- Report
{{ fetchSolutionsError }}
-
-
Your rendered github-flavored markdown will appear here.
-
Label this discussion...
-
No Label
Keep the comment unlabeled if none of the below applies.
-
Issue
Use the issue label when reporting problems with the kata.
Be sure to explain the problem clearly and include the steps to reproduce. -
Suggestion
Use the suggestion label if you have feedback on how this kata can be improved.
-
Question
Use the question label if you have questions and/or need help solving the kata.
Don't forget to mention the language you're using, and mark as having spoiler if you include your solution.
-
No Label
- Cancel
Commenting is not allowed on this discussion
You cannot view this solution
There is no solution to show
Please sign in or sign up to leave a comment.
Description grammar fixes
PHP translation kumited
Ummm... I think there may be an issue with the random test cases.
st = 'Aqfexodf Znynryox A Xhxfteqc Rhovr Gd Fnam Lnxdm' 'A Gd Fnam Lnxdm Rhovr Aqfexodf Xhxfteqc Znynryox' should equal ' A Gd Fnam Lnxdm Rhovr Aqfexodf Xhxfteqc Znynryox'
this pattern seems to carry over frequently with an extra ' ' before the expected string which.... is unexpected ? ig ?
Note: there's an additional space somewhere in st that is lost in markdown here.
I agree that the kata is currently incorrect in python. Specifically, test gen produces length-0 words and the reference solution treats length 0 words as words that get sorted first.
It's kind of an interesting test case to have additional spaces/empty words, but as the description doesn't mention it I believe that the test gen is wrong to produce these and should instead produce words of at least length 1 with a single space between each. It's also common for words to ignore empty words, so it is strange to pick this particular definition of word.
random tests will not generate words of 0 length now.
This comment has been hidden.
Either way, thanks.
JavaScript fork
Merged.
In JS: tests should not generate fixed length of 8 words only in string
Should be fixed.
python new test framework is required. updated in this fork
Approved
depending on how one interprets the word word, this is either wrong or it changes the spec.
see issue above.
JS: Node v12 should be used enabled along with its appropiate assertion tools (Mocha + Chai).
Updated to Node 18.
Approved
Not original.
I'm sorry. I don't understand. I formed the kata and also made the solution on my own.
So you independently replicated something that has been done dozens of times on here.
Hey, I believe you did it yourself. But that doesn't make it original.
Codewars is full of kata that ask to sort lists on various attributes of elements.
Oh well. I'm sorry about that. It's my first kata here and I thought I was doing something original since I came up with it myself. I've seen a lot of katas here copied from sites like projecteuler and rosettacode though (even 4kyu ones). I'll do better next time. Can this issue ever be resolved then?
Uhm. You could try to unpublish all the other kata that ask to sort a list ..
(Hint: you can only unpublish your own kata.)
Original hmm ... I don't think codewars has a storage limit or disk limit for more <10kb datas . Anyway , from what i know base theme of Codewars is practice makes perfect . so having completed many katas that requires sort list with different keys will help to practice . People can always ignore them if they think they are on high level . And he made this kata and cases ( better than copying from sites ) so i think discouraging him is a bad idea . maybe he can create some awesome kata's in future
From the Kata Best Practices: Make Sure Content is New.
Also, I am trying my darnedest in the face of Eternal September to encourage (new) people to solve kata, learn from them, and create awesome kata (instead of repetitive drivel). Pixie had the bad luck to be the second person today (and the umpteenth this week) I was telling his idea wasn't new, and no, I have not been as verbosely encouraging as I might have been.
I do appreciate your advice. I'll make sure to follow it from next time. However, I'm going to resolve this issue as it does not have a direct relation with the performance of the kata.
It's not a problem as long as it's not a duplicate ;-)
We disagree.
If somebody creates a kata that is essentially the same as an existing kata, it's not new. It doesn't have to be an exact duplicate to go against the spirit of "Make sure content is new".
But I can't stop you from gathering points by approving everything you stumble over.
If you're going to raise an issue saying a kata is a duplicate, you need to link to the kata in which this kata is a duplicate of.
Otherwise allegations will fly all over the place, and nobody will know if the kata is actually an exact duplicate. It also generates lots of noise which makes actual duplicates harder to be noticed.
Also, you can't talk about "content is new" without an objective criteria, or else we can nuke out over half of the white/yellow katas already, since for except the stories and reading comprehensions required they're sure nothing new ;-). That's not the way to go. You might just as well strip all of them and say "implement the algorithm which does this".
(Or, of course, you can simply point it out without marking it as an
issue
, then we'll all assume that you don't think that's something that needs to be addressed.)We could.
Well, that's your opinion.
Can I have mine?
javascript translation kumited (:
Approved! :D
Random tests always have an extra space after all the words, so there is actually an extra group of zero characters (which is probably out of spec).
Thanks for pointing it out!! I had forgotten to remove that. The issue has been resolved.
This comment has been hidden.
So sorry! Corrected now :)
you striped
a
at the wrong place. I edited the kata, it's good, now. ;)Wow. Thanks a lot. I just realised that I was wrong and was trying to correct it. Sorry for being a noob .-.
no problem ;)