coder13 / coder13/comp-task-management
Persist task and category generation
Open
- Dominant language
- TypeScript
- Stars
- 0
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
Tasks and categories should be persisted in the backend.
Contributor guide
No contributing guide indexed for this repository
Research direction
The issue does not name files, tests, or a backend entry point. Start by locating where tasks and categories are generated and how the GraphQL backend currently handles them, then determine the persistence approach and its required schema. Done means generated tasks and categories remain available through the backend rather than existing only temporarily.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- graphql, nextjs, nodejs, typescript
- Domain
- api, backend, databases
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100