j
/
punchclock
1
0
Fork 0
Code Issues 3 Releases 1 Activity

handle multi-day intervals #2

New Issue
Open
opened 2023-07-20 07:39:31 +02:00 by j · 0 comments
j commented 2023-07-20 07:39:31 +02:00
Owner
Copy Link

for simplicity the script assumes that intervals always are contained in a single UTC calendar day.

If you work late in the night this assumption will break and the behaviour is not clear right now.

The solution probably lies in the _get_active_seconds_for_day function to automatically expand incomplete intervals (either missing start for this day, or stop for any day in the past).

for simplicity the script assumes that intervals always are contained in a single UTC calendar day. If you work late in the night this assumption will break and the behaviour is not clear right now. The solution probably lies in the `_get_active_seconds_for_day` function to automatically expand incomplete intervals (either missing start for this day, or stop for any day in the past).
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
main
0.0.1
Labels
Clear labels
No items
No Label
Milestone
Clear milestone
No items
No Milestone
Assignees
Clear assignees
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Reference: j/punchclock#2
No description provided.
Delete Branch "%!s(<nil>)"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?