CMU-313 / CMU-313/fall-26-opencode-team-zero
As a developer, I want project-copy failure to return a clear, concise message describing what went wrong so that I can understand and fix the problem.
Open
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 0
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
Total: 11/20
Impact: 6/10
This is an addition to the previous user story.
Effort: 5/10
Having error messages will probably come with the development of the copy of current directory feature
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 previous user story and the implementation of the current-directory project-copy feature. Trace where project copying can fail and identify the existing error-handling path. Done means failures return clear, concise messages that explain what went wrong and help the developer fix the problem.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 48/100