-
Notifications
You must be signed in to change notification settings - Fork 643
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
Feature#bound date #446
Feature#bound date #446
Conversation
I'm having trouble understanding the new code. Can you add some code comments? |
5cd549e
to
a0cfa0f
Compare
I added a few comments, tell me what is not clear enough. |
Make sure you review this commit QuentinFchx@daf8e68 |
@jonthornton Do you think you'll find the time to review this one ? |
It may have to wait until the weekend, but I'll get to it. Sorry for the On Tue, Oct 13, 2015 at 3:45 PM Quentin [email protected] wrote:
|
No worries, I already found an issue in my |
a0cfa0f
to
e85e89e
Compare
With those changes, I ran into an issue with time changes. A better approach maybe to be able to pass a function to calculate
I will try this way. |
I found another solution with passing a function to compute durationString. As this use case might be too specific, i'll go with my fork. |
That's a great idea! |
boundDate
is a date object bound to the selected time. Its purpose is to be computed againstdurationTime
to be able to display a duration over 24h.I also linted the file:
eqeqeq,
pad2
+stepval
not used, loop var declared as global.TODO: boundDate description for the README.
Closes #423