-
Notifications
You must be signed in to change notification settings - Fork 24
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
End time default value #58
base: develop
Are you sure you want to change the base?
End time default value #58
Conversation
); | ||
}; | ||
``` | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This example is not related to the rest of the PR. I would advise against it.
fireEvent.click(getByRole('button')); | ||
|
||
act(() => { | ||
jest.advanceTimersByTime(30000); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You need to advance time by more than 30000 to really test that the timer will stop at 0. I would replace 30000
by 40000
for example.
initialTime = 0, | ||
interval = 1000, | ||
onTimeOver, | ||
onTimeUpdate, | ||
step = 1, | ||
timerType = 'INCREMENTAL', |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I would keep the alphabetical order of properties, to keep the author's logic.
Hey, can we push this? Should I fix the reviews? |
endTime
value changes depending on timer mode