Kata

Your test ('A0', 'B0', 2). From 'A0' to 'B0' or 1 note(!), or 2 semitones. ('F4', 'B4', 4). From 'B4' to 'F4' or 4 notes(!), or 6 semitones. So what we searching???

Melodic and harmonic intervals are named for the distance from one letter name to the other letter name, first and last note inclusive

('A0', 'A0') => 1 (unison) ('A0', 'B0') => 2 (second)

This is standard convention for musicians. The ordinal number is then paired with a modifier such as 'major', 'minor', 'perfect', etc... but that is beyond the scope of this kata

It measures Degree intervals (of the Major Scale), regardless of the Pitch intervals between degrees, starting with value 1 for the zero distance interval. As author mentioned, each letter represents such degree. Octave numbers are added to be able to measure degree intervals across octaves.

well, the wording is still totally awful, for non musicians... XD

Intervals are named for the distance, first note inclusive, between the lower note and the higher note. >>> This distance is measured not in semitones or whole tones, but rather in note names spanned. <<<

This will make a lot of other languages unhappy.

How?

It's not ideal, it's not necessary, but I fail to see how this is an Issue. It doesn't break the kata, does it?

If your standard is as low as "it doesn't break the kata" then everything is fine (it also explains why beta katas are so horrible I suppose). However katas are also meant to teach good practices: when a kata can't even use the most natural, sense making input format this cannot be count as good practice.

Note that in almost all strongly typed languages there are no way to specify your input is an array with exactly 2 elements (and no, tuple isn't one, that's a completely different construct). Once this happens, you're opening a massive source of error for everyone: Will the tests accidentally put more or less elements? Do I need to validate this as a user? Will some translator decide to do a dick move and make users mandatory to validate this? Given the average quality of CW katas, especially translations, these can all happen, and they're all solved by choosing a type that isn't literally retarded for the job. So I don't see why this issue has to be put under the rug for the general desire of "pushing every beta kata past approval ASAP".

Thanks! I've made various changes in response to the issues noted in discourse here. Would you update the translation so I can approve and resolve?

Updated: https://www.codewars.com/kumite/63fab99d4776ef4c7ef2cf73?sel=63fc5d63b15a215e8c3018c1

I was already worried about all that stuff for this one. Fortunately, it didn't assume prior knowledge, didn't go beyond every existing piano in the world, and didn't expect me to deal with those ridiculous irregular half note intervals. Also, simple input parsing. Sometimes I just don't want all those complications, you know?

It's not a bad idea, but it's a different kata, and it needs specs on par with this one.

Other opinions are undoubtedly available. :]

sure, but author had estimated rank of 6 kyu, so I hinted about options to make this actually a 6 ;)

I just voted 7 :P

From a quick scan of the internet, it seems most authors who use the term "Pitch Interval" are referring to an interval measured in semitones, whereas here I am referring to the interval size measured across note letter names (typically stated as an ordinal number such as 3rd or 4th), which is generally paired with an interval quality (such as major or perfect).

I understand you want to differentiate between rhythm intervals and pitch intervals. How about "Find the Letter Note Interval Between Two Notes"? Or "Find the Melodic Interval Between Two Notes"?

melodic interval seems fine

Time to republish?

Thanks for the feedback. I'll work on it.

This is the first time I've created a kata, and I'm not familiar with the correct process for incorporating others' work. Your solution was clearly better than my first attempt; is is acceptable for me to update this kata with your solution as the reference solution?

Much better! :]

You still have an undeclared variable, now in getRandomNote. If it's white, it's suspect. It should be orange.

Got it; fixed. 👍🏼