feat: add child actions menu specification for ParentView
Some checks failed
Chore App Build, Test, and Push Docker Images / build-and-push (push) Failing after 1m37s
Some checks failed
Chore App Build, Test, and Push Docker Images / build-and-push (push) Failing after 1m37s
This commit is contained in:
@@ -59,6 +59,10 @@
|
||||
|
||||
## Backend Implementation
|
||||
|
||||
- child_api.py will need it's /child endpoint modified so that in child mode, only the chores (tasks with is_good = true) that are not scheduled, or scheduled for that current day to be returned.
|
||||
- a new child_api endpoint may need to be created to extend time on a chore that has expired it's time.
|
||||
- should a new tinyDB database file be used for scheduling since each child has a potential calendar?
|
||||
|
||||
## Backend Tests
|
||||
|
||||
- [ ]
|
||||
|
||||
67
.github/specs/feat-child-actions.md
vendored
Normal file
67
.github/specs/feat-child-actions.md
vendored
Normal file
@@ -0,0 +1,67 @@
|
||||
# Feature: A new menu should be displayed when a child's card is clicked in ParentView. This menu will feature actions that a parent can perform on a child.
|
||||
|
||||
## Overview
|
||||
|
||||
**Goal:** When in parent mode, clicking on the child's card will bring up a menu that will have several items to issue actions on the child.
|
||||
|
||||
**User Story:**
|
||||
As a parent, when I click on the child's card in parent mode, I want to be presented with a menu that displays the following:
|
||||
|
||||
- Award Certificate
|
||||
- Award Badge
|
||||
|
||||
**Rules:**
|
||||
follow .github/copilot-instructions.md
|
||||
|
||||
---
|
||||
|
||||
## Data Model Changes
|
||||
|
||||
### Backend Model
|
||||
|
||||
### Frontend Model
|
||||
|
||||
---
|
||||
|
||||
## Backend Implementation
|
||||
|
||||
## Backend Tests
|
||||
|
||||
- [ ]
|
||||
|
||||
---
|
||||
|
||||
## Frontend Design
|
||||
|
||||
When the child card is pressed, the router should move to a page that presents the menu items. Or should it be a dropdown menu. it seems like having a seperate page with the options provides better UX.
|
||||
|
||||
When the menu item is clicked, we should stub out the action for now, Awarding achievements and badges will be done in a future spec.
|
||||
|
||||
## Frontend Implementation
|
||||
|
||||
## Frontend Tests
|
||||
|
||||
- [ ]
|
||||
|
||||
---
|
||||
|
||||
## Future Considerations
|
||||
|
||||
Eventually, there will be a new view that shows to create a certificate for the child. In this view, a parent can write information about the certificate. The certificate will show the next time a child clicks on themselves in child mode.
|
||||
Eventually, parents will be able to reward badges similar to certificates the the child.
|
||||
|
||||
## Questions
|
||||
|
||||
- Should badges be removable? For example, if there is a badge that represents most chores done in a week, that badge may move from one child to another. If removable, should that option also be presented under the new menu?
|
||||
|
||||
---
|
||||
|
||||
## Acceptance Criteria (Definition of Done)
|
||||
|
||||
### Backend
|
||||
|
||||
- [ ]
|
||||
|
||||
### Frontend
|
||||
|
||||
- [ ]
|
||||
Reference in New Issue
Block a user