Fix: timeclock: allow overlapping sessions with same account name #2422
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR fixes a regression that broke existing timeclock files containing overlapping sessions with the same account name. The issue was in
pairClockEntries
function which added a validation that prevented clock-in entries for accounts that already had active sessions.However, the existing
findInForOut
logic already had handling for multiple sessions with the same account name usingpartition
to correctly pair clock-ins with clock-outs.Closes #2417
Added test