Add run deletion guard to genlocke edge cases bean
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
This commit is contained in:
@@ -1,11 +1,11 @@
|
||||
---
|
||||
# nuzlocke-tracker-k7ot
|
||||
title: Genlocke management in admin panel
|
||||
status: in-progress
|
||||
status: completed
|
||||
type: feature
|
||||
priority: normal
|
||||
created_at: 2026-02-09T08:38:13Z
|
||||
updated_at: 2026-02-09T09:43:04Z
|
||||
updated_at: 2026-02-09T09:51:51Z
|
||||
parent: nuzlocke-tracker-25mh
|
||||
---
|
||||
|
||||
|
||||
@@ -12,6 +12,6 @@ Collect and evaluate edge cases for genlocke tracking. Review periodically to de
|
||||
|
||||
## Edge Cases
|
||||
|
||||
- [ ] What happens if a genlocke run is manually deleted? (The GenlockeLeg would still reference a non-existent run_id)
|
||||
- [ ] Prevent run deletion if the run is linked to a genlocke leg. The `DELETE /runs/{id}` endpoint should check for a `GenlockeLeg` with matching `run_id` and return 400 if found, telling the user to remove the run from the genlocke first.
|
||||
- [ ] What happens if a user tries to advance a leg twice? (Currently guarded by "next leg already has a run" check)
|
||||
- [ ] What if the user edits a completed run back to active after the genlocke has already been marked completed/failed?
|
||||
@@ -1,11 +1,11 @@
|
||||
---
|
||||
# nuzlocke-tracker-x4p6
|
||||
title: Genlocke overview page
|
||||
status: in-progress
|
||||
status: completed
|
||||
type: feature
|
||||
priority: normal
|
||||
created_at: 2026-02-09T07:42:19Z
|
||||
updated_at: 2026-02-09T09:33:02Z
|
||||
updated_at: 2026-02-09T09:40:02Z
|
||||
parent: nuzlocke-tracker-25mh
|
||||
blocking:
|
||||
- nuzlocke-tracker-lsc2
|
||||
|
||||
Reference in New Issue
Block a user