Maybe I'm just really tired right now, but I don't see a test where that would fail like that. Can you check the test cases and let me know which ones are causing problems?
It's case insensitive meaning that the input is interpreted the same way regardless of case.
Case sensitive means that it will have a different meaning. For example, user input of 'Poor' vs 'poor' would give different results if it were case sensitive.
Seems more clear to me. It could still be still clarified about leftover cubes and how many cubes need to be in each row in relation to other rows, because it can greatly change the response. Unless you want part of the challenge to be working out the architecture, of course :).
I think there needs to be some clarification on what is considered a pyramid. Does the next higher level need to be only 1 cube smaller than the one below it, or does it simply have to be smaller (by any amount)? Does the top level always need to consist of one cube only? Can there be cubes left over?
Your example seems to indicate that as long as the next level above is smaller, then it's fair game, but other than that the rules for pyramid building unclear.
Minor typos - for the last 2 examples in the description the function is written as horse(4) & horse(1) rather than the plural horses(n) used everywhere else.
One thing that could be clarified is what to do if the input is both less than 3 and not an integer (like 2.5). It's unclear which rule should be followed in this case.
the last line of the description says "Because you're a nice person, you always round up the tip, regardless of the service."
16.1475 should round up to 17 in this case.
Done :). Thanks!
Maybe I'm just really tired right now, but I don't see a test where that would fail like that. Can you check the test cases and let me know which ones are causing problems?
It's case insensitive meaning that the input is interpreted the same way regardless of case.
Case sensitive means that it will have a different meaning. For example, user input of 'Poor' vs 'poor' would give different results if it were case sensitive.
Hey I'm marking this as resolved as it does not seem to be an issue with the kata. If I am incorrect let me know and I will look into it further!
Seems more clear to me. It could still be still clarified about leftover cubes and how many cubes need to be in each row in relation to other rows, because it can greatly change the response. Unless you want part of the challenge to be working out the architecture, of course :).
I think there needs to be some clarification on what is considered a pyramid. Does the next higher level need to be only 1 cube smaller than the one below it, or does it simply have to be smaller (by any amount)? Does the top level always need to consist of one cube only? Can there be cubes left over?
Your example seems to indicate that as long as the next level above is smaller, then it's fair game, but other than that the rules for pyramid building unclear.
The tip always needs to be rounded up :).
Thanks for the translation :)
@pet_dinosaur had the same error and found a solution. Perhaps you could check out their comment.
Cool ☺. Marked it as resolved.
Minor typos - for the last 2 examples in the description the function is written as
horse(4)
&horse(1)
rather than the pluralhorses(n)
used everywhere else.One thing that could be clarified is what to do if the input is both less than 3 and not an integer (like 2.5). It's unclear which rule should be followed in this case.
Nice kata!
You have a bug in your code. Double check for invisible characters.
This comment is hidden because it contains spoiler information about the solution
This comment is hidden because it contains spoiler information about the solution
Loading more items...