Thanks!

You're right, my mistake! I've been looking at it too closely. I'll change the description to say that you can work it out from the given clock faces, not the ones that equate to '6.30'

Thanks! Glad you enjoyed it

Javascript: CHAR_TO_MORSE
Ruby: $CHAR_TO_MORSE
Pyhton: CHAR_TO_MORSE

The dictionary is simply an object called CHAR_TO_MORSE that holds values and their equivalents. So call upon it as you would a regular object.

Thanks, Dan. Yeah you're right, I'll try and make it clearer in the description!

Great, thanks!

Done!

I'll mark it as resolved

It's called: CHAR_TO_MORSE

and it's written within the initial solution -->

Javascript: //CHAR_TO_MORSE preloaded to convert characters into Morse code.
Ruby: #$CHAR_TO_MORSE preloaded to convert characters into Morse code
Pyhton: #CHAR_TO_MORSE preloaded to convert characters into Morse code

I'll add it into the description to make it clearer!

The reverse is a little bit trickier than this one but I'll give it a go!

The test cases are always precise because they provide an input and a specific solution that must be returned. It is not the fault of the test case itself but I'm guessing it could be a rounding issue embeded within the code. If both versions pass the tests then essentially they are both correct, even if one method is more precise than the other.

I've since changed the name to CHAR_TO_MORSE