Repository navigation
Wrong time calculation when startTime after endTime (manual edit) #79
Description
The item with 33 minutes has properties: startTime=2021-03-02T16:34:33.525, endTime=2021-03-02T16:00:37
{{ message }}
The item with 33 minutes has properties: startTime=2021-03-02T16:34:33.525, endTime=2021-03-02T16:00:37
Activity
#79: using DateFormatter logic now also to calculate overall project …
#79: using DateFormatter.getSecondsBetween now at all places were sec…
#79: disabling save button now when input is not valid
#79: fixed sonar issue
#79: made time comparison easier to read
Merge pull request #82 from doubleSlashde/bugfix/#79_preventNegativeW…
JSchraff commentedon Apr 14, 2021
with #82 it is no longer possible to create Dates with negative duration. #80 will not be merged for now. It is still necessary to unify the use of DateFormatter and Duration. It should not be obfuscating the existence of negative durations, because this could lead to missunderstandings and hampers the ability to spot Problems.
Therefore it should be formatted to show the negative Time everywhere correctly if somehow a negative Time gets created, or in future it is necessary to support negative work times.
Set up CI with Azure Pipelines (bugfix/doubleSlashde#79)
Death111 commentedon Jul 11, 2023
I also noticed that "absolute time" is calculated wrongly when there are overlapping times.
It can also be discussed on what is expected behavior here. As if both items would be "work" we would have absolute time 1h and work time displayed as 2 h - which is also confusing