• ###### FArekkusuresolved an issue on "Tick Toward" kata

My solution involves finding all of the integral points along the line between start and target, moving "diagonally" as mentioned in the description

If you can't pass the tests, then you're "moving diagonally" incorrectly.

• ###### mcruggierocreated an issue for "Tick Toward" kata

The description seems vague. My solution involves finding all of the integral points along the line between start and target, moving "diagonally" as mentioned in the description. However, reading a prior issue with (3,2), (4,5), it seems there is a limit the max length of each diagonals. Please update the max length, are diagonals limited to 2^.5 ?

Thanks!

• ###### yannickjmtcommented on "Tick Toward" kata

New to ruby, is that forbidden? Weird that it makes the random tests fail but not the others.

• ###### FArekkusuresolved an issue on "Tick Toward" kata

Ruby version is working correctly. And you're most probably mutating the input.

• ###### yannickjmtcreated an issue for "Tick Toward" kata

Ruby random tests verification uses the same value for target and start. But the function is fed different values (Same issue reported by @sergeyn 3 years ago).

Rand test 1
start = [7, 7]
target = [0, 5]

wrong route from [0, 5] to [0, 5] - Expected: [[0, 5]], instead got: [[7, 7], [6, 6], [5, 5], [4, 5], [3, 5], [2, 5], [1, 5], [0, 5]]

Looks good.

• ###### FArekkusucommented on "Tick Toward" kata

@Unnamed, the description was updated. Can this issue be closed, or is it not clear enough yet?

• ###### Blind4Basicscommented on "Tick Toward" kata

Note: you should move diagonally until the path from your current position to the target cannot be represented as fully horizontal/vertical line.

• ###### FArekkusucommented on "Tick Toward" kata

I've modified the description yesterday (while writing the translation) clarifying this point, but all the changes are missing O_o

Edit: the last revision was 2 months ago, so the update never happened for some reason...

The description should be updated with the info from here.

• ###### Blind4Basicscommented on "Tick Toward" kata

For x and y, you "tick" by one at each step until you reach the max value on that axe, then you keep it constant. meaning you cannot have multiple times the same value unless it's the final one. It's obscur, yes, but I honestly already encountered worse about the descriptions, without any issue raised.

so, we resolve?

• ###### Unnamedcreated an issue for "Tick Toward" kata

The expected behavior for the case with multiple shortest routes is unspecified.

@Blind4Basics 'NOTE: x should "tick towards" target_x indepedently of y. Same with y.' doesn't really mean anything. Of course they are independent, but how does it help to choose between `[[3,2],[4,3],[4,4],[4,5]]` and `[[3,2],[3,3],[3,4],[4,5]]`?

• ###### FArekkusucreated a suggestion for "Tick Toward" kata

Python translation. Please, review and approve (the author is inactive).

• ###### FArekkusuresolved an issue on "Tick Toward" kata

The fact that you can move diagonally doesn't mean that you have to. Also, duplicate issue.