Northeastern-Electric-Racing / Northeastern-Electric-Racing/FinishLine
Change Request Overview - Move Logic To Endpoint
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 36
- Forks
- 9
- Avg merge
- 4d 21h
- Merged PRs (30d)
- 11
Description
Description
We Have a lot of logic for getting a persons relevant change requests in the frontend of the change request overview page. We want to move this logic to the backend.
Acceptance Criteria
[ ] - Route on “change-requests/overview” as a get with no arguments
[ ] - Controller function gets the current user and passes it into the service function
[ ] - Service function uses the same logic as the frontend right now to return all the relevant wbs elements to the frontend.
[ ] - Unit tests making sure this works
[ ] - Screen shots of manual tests to the endpoint
Proposed Solution
^
Mocks
No response
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.
Research direction
Start by tracing the frontend logic for the change request overview and identify the current route, controller, and service structure. Implement the GET change-requests/overview endpoint with the current user, preserve the relevant WBS-element behavior, add unit tests, and manually verify the endpoint with screenshots.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- backend-api-design
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 32/100