ClockGU / ClockGU/clock-backend
Zero length shift
Open
enhancement
high-priority
- Dominant language
- Python
- Stars
- 0
- Forks
- 4
- PR merge metrics
- No merged PRs in 30d
Description
I'm not sure why we haven't thought of this validation or why this only now became a problem:
On shift creation we need to validate if `started == stopped` as we do [here](https://github.com/ClockGU/clock-frontend/pull/696) in the frontend.
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.