SaiKrishna add donut chart route and controller for planned cost breakdown

[saikrishnaraoyadagiri]

Description

Summary Dashboard: Create a Donut Chart showing Planned Cost Breakdown by Type of Expenditure (WIP Sai Krishna)

The chart should display four categories: Plumbing, Electrical, Structural, and Mechanical, each represented by a different color.
The percentage of the total cost for each category should be displayed next to it in hover text.
Include two filters:
A Project filter to view the cost breakdown for a specific project.
Backend Requirements
API Endpoint:
GET /api/projects/:id/planned-cost-breakdown
Data Structure:
{
plumbing: 5500,
electrical: 4800,
structural: 7600,
mechanical: 6300
}
Database Schema:
{
projectId: ObjectId,
category: String, // Plumbing / Electrical / Structural / Mechanical
plannedCost: Number
}
Data Retrieval Logic:
Query by projectId.
Group planned costs by category.
Sum up planned costs per category.
Return structured breakdown.

Related PRS (if any):

To test this backend PR you need to checkout the #4011 frontend PR.
…

Main changes explained:

• Added plannedcostcontroller.js, plannedcost.js, plannedcostrouter.js
• updated routes.js
  …

How to test:

1. check into current branch
2. do npm install and ... to run this PR locally
3. Clear site data/cache
4. log as admin user
5. Go to http://localhost:4500/api/projects/:ProjectId/planned-cost-breakdown (replace the project id with the actual project id). I have set up the data for this project id 68747d37c71d9f67ac207eef
   http://localhost:4500/api/projects/68747d37c71d9f67ac207eef/planned-cost-breakdown
   6.You can setup the data for other project ids and can test. you need to setup the data in this collection " plannedCosts"
6. Each type can have multiple entries with different costs in the same project and when we hit the api we should get the combined costs

Screenshots or videos of changes:

[aditya2512]

The new API endpoint /api/projects/:id/planned-cost-breakdown leverages MongoDB aggregation to accurately sum planned costs by category for each project, which is ideal for powering a frontend donut chart. The aggregation pipeline is both efficient and easily extensible the $match, $group, and $project stages are well-organized and target the most common reporting needs (Plumbing, Electrical, Structural, Mechanical). I appreciate the use of service/controller layering for separation of concerns, and the parameter validation on projectId reduces risk of erroneous queries.
Returning the results as a category keyed flat object is optimal for direct consumption on the frontend, minimizing data transformation.

[Anusha-Gali]

Hi Sai Krishna,

I have reviewed your PR locally and have mentioned issues with the frontend. The backend API response is as expected

[one-community]

Thank you all, merging!