For example, imagine a CircularList of [1, 2, 3, 4]. Five invocations of next() in a row should return 1, 2, 3, 4 and then 1 again. At this point, five invocations of prev() in a row should return 4, 3, 2, 1 and then 5 again
In the second statement, shouldn't 5 invocations of prev() return 4, 3, 2, 1 and then 4 again?
Not really related to the kata itself, but I can't seem to find my own solution to this kata. It's not in the "My Solutions" tab, nor in "All Solutions". Yet, I can still see the "Solutions" page, and I did not forfeit the kata. Is there a problem?
If your tests require HTML elements to have specific ID values, and state with specific property names, it's probably better to mention those in the description/requirements, rather than having the user figure it out by looking at the tests for each possible value.
has an initial state containing name, wish and priority
has an text area with id 'wish'
has 'priority' drop-down with values from 1-5
it('should change state when entering Peter as name', () => {
form.find("#name")
This comment is hidden because it contains spoiler information about the solution
In the second statement, shouldn't 5 invocations of
prev()
return 4, 3, 2, 1 and then 4 again?Not really related to the kata itself, but I can't seem to find my own solution to this kata. It's not in the "My Solutions" tab, nor in "All Solutions". Yet, I can still see the "Solutions" page, and I did not forfeit the kata. Is there a problem?
This comment is hidden because it contains spoiler information about the solution
I don't jump in with pointless and offensive comments to other people's posts.
I don't remember asking for your input.
Created a Java translation. Please review.
Thank You! Very nice kata, looking forward to more of such DS katas.
Java translation is up. Please review.
This comment is hidden because it contains spoiler information about the solution
If your tests require HTML elements to have specific ID values, and
state
with specific property names, it's probably better to mention those in the description/requirements, rather than having the user figure it out by looking at the tests for each possible value.This comment is hidden because it contains spoiler information about the solution
This comment is hidden because it contains spoiler information about the solution
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...