[Frontend] - Deleting WPs should accept a change request ID
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 62/100
- Issue type
- Feature
- Clarity
- Clearly specified
- Activity status
- Stale
- Tech stack
- typescript
- Domain
- frontend
Research direction
Start after resolving the dependency on issue #1587. Review DeleteWorkPackageView.tsx and the change request dropdown component, then update the related functions in work-packages.api.ts and work-packages.hooks.ts. Done means the deleting work package form requires selecting a change request ID and passes that ID through the deletion flow.
Written by the indexing model from the issue text.
Description
Make these changes on a new branch: feature/cr-delete-wp
Blocked by: #1587
Description
The deleting WP form should take in a change request ID to be deleted.
Acceptance Criteria
Deleting a work package require the user to select a change request first.
Proposed Solution
- Use the change request dropdown component to select the change request in
DeleteWorkPackageView.tsx work-packages.api.ts: update the delete work package function to accept acrIDwork-packages.hooks.ts: update the delete package hook to accept acrID
- Dominant language
- TypeScript
- Stars
- 36
- Forks
- 9
- Avg merge
- 4d 21h
- Merged PRs (30d)
- 11
Contributor guide
No contributing guide indexed for this repository
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.
More from Northeastern-Electric-Racing/FinishLine
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
maintenance
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
maintenance
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
-
back-end draft
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
back-end draft
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
All issues in Northeastern-Electric-Racing/FinishLine
Similar issues
-
comp/dashboard P3 type/bug
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
NousResearch/hermes-agent#117722 ·
-
clawsweeper:fix-shape-clear clawsweeper:queueable-fix clawsweeper:source-repro impact:ux-friction issue-rating: 🦞 diamond lobster no-stale P3
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
community first-timers-only good first issue hacktoberfest help wanted low hanging fruit up-for-grabs
Difficulty 1/5 Under an hour Newbie friendliness 76/100
-
code-quality refactoring
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
github/gh-aw-firewall#8816 ·
-
integration:quickjs org:external priority:backlog topic:code-interpreter topic:middleware type:feature
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
langchain-ai/deepagents#6450 ·