Northeastern-Electric-Racing / Northeastern-Electric-Racing/FinishLine
[Executive Summary] - getVehicleDevelopmentSummary 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 an endpoint to get the Vehicle Development graph data for a given executive summary. This data should include the set of projects that ran during that season, filterable by team, so the frontend can render the Gantt-style timeline bars (shown in image below). This can go in exec-summaries.services.ts , exec-summaries.controller.ts, etc.
Acceptance Criteria
- endpoint accepts an executiveSummaryId and optional teamId (for filtering) and returns a VehicleDevelopmentSummary
- return values only include projects/work packages that fall in the given executive summary's season start/end dates.
- filtering by team only returns projects associated with that team, no filter includes all projects
- transformer for VehicleDevelopmentSummary
Proposed Solution
- Create transformer for VehicleDevelopmentSummary
- Create route, controller, and service functions for the getVehicleDevelopmentSummary endpoint
Mocks
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 with exec-summaries.services.ts and exec-summaries.controller.ts, then inspect nearby endpoint patterns and the existing VehicleDevelopmentSummary shape. Implement the route, controller, service functions, and transformer described in the issue. Done means the endpoint accepts an executiveSummaryId and optional teamId and returns only matching projects within the executive summary season dates.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- api, backend
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 68/100