You need to sign in or sign up before continuing.×
6 kyu
Turn String Input into Hash
891 of 2,729user4655293
Loading description...
Parsing
Algorithms
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.
Funny Kata! thnx
It might be fun to have more complex tests :D like:
Nice kata, congratulations, well done.
Nice one. Really like it
Description of the cata is false - decision doesn't require Symbol as a key of hash-object. I'm not satisfied.
Python translation please check and aprove
.
This comment has been hidden.
Just the other day I read here on Codewars from someone who complained about so-called "Gotcha" Katas. This is one of them. I am beginning to understand this very well! Just, why?? Why can't you write in the description the actual, or better, the complete problem? is this really such an uplifting "hihihihi" moment?
Why not put one of the more complex inputs - at least just ONE - in the test section too, rather than "Gotcha!" at Attempt first.
sry for the rant - have a nice weekend everyone!
It seems to me that you have made an assumption that we know what you are talking about, but I should point out that's not the case. What exactly you want?
Hello, if the "Gotcha" topic I mentioned doesn't trigger you, then it looks like you're not affected by it either. Otherwise, I have described as briefly as I could what it is about. For the rant in it i apologize again, but sometimes this must also be said
Unlike stated, sometimes we receive a string with a different format of the one given in the description (no space after the comma).
This is the case for Ruby random tests.
Possible, when I wrote the message the JS translation was not approved yet.
Should both translations be aligned in test cases?
No. But both should match with the description.
test.expectThus this solution works fine...
fixed. took only 5 mins, not years.
JS translation updated.
; ) )
Thanks :)
JS translation kumited.
(Description modified (examples) & random tests added) more info on how to approve it ( or not )
Is this test correct?
Its green for me but kata still fails with 'expected nil' error like for other guys. I must be missing something obvious.
OP left the building, closing!
Test Failed: Got {:a=>"1", :b=>"2", :c=>"3", :d=>"4"} why?
This comment has been hidden.
I've been having the same problem; my code is creating the proper hash, but it's saying that there's no split function for nil . . . not sure why this is happening. If there's a possibility that the input will be nil, that should be mentioned in the description. Or something's not working correctly.
That got me for a second. Then I looked at the example again
This comment has been hidden.
thats ok i found mistake thx