Skip to content
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

Evaluate necessity of corrected max working time check in timesheet #83

Open
gstuer opened this issue Apr 18, 2020 · 1 comment
Open
Assignees
Labels
enhancement New feature or request

Comments

@gstuer
Copy link
Contributor

gstuer commented Apr 18, 2020

Evaluate necessity of corrected max working time check ensuring timesheet's integrity
Is this check really needed to ensure that the timesheet's instances are correct or is it adequate to check this in the Checker instances. What problems could appear? How can we solve these problems?

Originally posted by @gstuer in #79

@gstuer gstuer added the enhancement New feature or request label Apr 18, 2020
@larsk21
Copy link
Contributor

larsk21 commented Apr 18, 2020

This is linked to the use of the TimeSpan class. I would propose to add a new data type for clock time, e.g. 07:15 or 23:45, and use the TimeSpan class for positive and negative "time vectors".

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants