Northeastern-Electric-Racing / Northeastern-Electric-Racing/FinishLine
[Executive Summary] - editExecutiveSummary endpoint
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 36
- Forks
- 9
- Avg merge
- 4d 21h
- Merged PRs (30d)
- 11
Description
Description
We need a editExecutiveSummary endpoint. This should go in a new file called exec-summaries.services.ts , exec-summaries.controller.ts , etc.
Acceptance Criteria
- only admin/ops team can edit executive summaries
- editExecutiveSummary service,controller,route methods
- unit tests
- postman test
Proposed Solution
- Create route, controller, and service functions for the editExecutiveSummary.
- Only admins/ops team can edit ExecutiveSummary
- for checking if a user is on the ops team, this should be implemented similarly to the isUserOnFinanceTeam function in reimbursement-requests.utils.ts
- Model after existing edit endpoint (ex: editGuestDefinition in recruitment.services.ts)
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 reviewing the existing editGuestDefinition endpoint in recruitment.services.ts and the isUserOnFinanceTeam function in reimbursement-requests.utils.ts. Add the requested methods in exec-summaries.services.ts, exec-summaries.controller.ts, and the corresponding route, then add unit and Postman tests. Done means admins and the ops team can edit executive summaries while other users are denied.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- api, authorization, backend
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 68/100