TemaDeveloper / TemaDeveloper/personal_planner
polish: No confirmation dialog for per-entry destructive deletes
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 2
- Forks
- 4
- PR merge metrics
- No merged PRs in 30d
Description
Description
Reaudit (2026-07-06): a ConfirmDialog already guards deleting a whole custom section (settings/page.tsx:901-927). But every per-record delete fires immediately with no confirmation:
sections/[slug]/page.tsx:356(weekly-grid Remove) anddeleteEntryat:109table-view.tsx:141/deleteEntry:35board-view.tsxdelete-card- budget / daily-log / goal-progress view deletes
work-tracker.tsx:244/331/428(session/expense/route)
Fix
Add a confirm step (reuse ConfirmDialog) or an undo-toast before per-entry/session/expense/route deletes.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the existing ConfirmDialog in settings/page.tsx:901-927, then trace the per-record delete handlers in sections/[slug]/page.tsx, table-view.tsx, board-view.tsx, the budget/daily-log/goal-progress views, and work-tracker.tsx. Done means every listed entry, session, expense, route, and card delete has a confirmation step or undo toast instead of firing immediately.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- nextjs, react, typescript
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100