Dharmik/backend/draw donut chart showing different types of material used backend resolving build

[Dharmik1710]

Description

Related PRS (if any):

None
…

Main changes explained:

• Added GET /api/bm/materials/:projectId API:
  Supports materialType query parameter to filter by material type.
  Supports increaseOverLastWeek=true to filter materials that have shown usage activity in the last 7 days.
  Returns: availableMaterials, usedMaterials, wastedMaterials, increaseOverLastWeek (percentage).
• Added GET /api/bm/projectsNames API:
  Returns only project _id and name fields from active projects.

How to test:

1. check into current branch

2. do npm install and npm run dev to run this PR locally

3. Get authentication token (normal user)

   • Make a POST request to:
     http://localhost:4500/api/login

   • Request body (replace with your own credentials):

      { 
         "email": "your-email",
         "password": "your-password"
      }
     
     

4. Get authentication token (BM Dashboard user)

   • Make a POST request to:
     http://localhost:4500/api/bm/login

   • Headers:
     Authorization: your-token

   • Request body (replace with your own credentials):

     {
       "email": "your-email",
       "password": "your-password"
     }
     
     

5. Test GET http://localhost:4500/api/bm/materials/{projectId}

   • Headers:
     Authorization: your-token (BM Dashboard user)

   • Query parameters optional:

     • materialType=material_id (Optional)
     • increaseOverLastWeek=true (Optional)

6. Test GET http://localhost:4500/api/bm/projectsNames

   • Headers:
     Authorization: your-token (BM Dashboard user)

7. Test GET http://localhost:4500/api/bm/materials/654946b2bc5772e8caf7e962

8. GET /api/bm/materials/:projectId with materialType filter
   http://localhost:4500/api/bm/materials/654946b2bc5772e8caf7e962?materialType=666215b5ce887b3a3337f17c
   

[sreeja013]

Tested GET /api/bm/materials/:projectId with and without materialType and increaseOverLastWeek filters → response correct.
Tested GET /api/bm/projectsNames → returns only _id and name.
Verified both login flows and token usage. All functionalities working as expected.
Screenshots attached.

[csk731]

I reviewed this PR by running the branch locally. Everything appears to be functioning correctly, and all API responses are as expected.

However, I was able to call the APIs using a normal user authentication token instead of a BM Dashboard token. If this behavior is intentional and aligns with the requirements, then everything looks good.

[sohailuddinsyed]

Tested both APIs as per the given instructions.

• GET /api/bm/projectsNames API returns only project _id and name fields from active projects as expected.

• GET /api/bm/materials/:projectId API supports the materialType query parameter to filter by material type and returns expected result.

• The API also supports increaseOverLastWeek query param to filter materials that have shown usage activity in the last 7 days and returns the expected values.

[ManviKishore]

Changes working as expected.

[suparshwa31]

I tested all the endpoints, and everything is working as expected.

[sirisudheeksha]

After signing in with both the regular and BM logins and sending requests with the tokens, I checked /api/bm/projectsNames, which returns just the project IDs and names. I hit the /api/bm/materials/:projectId endpoint both with and without the materialType and increaseOverLastWeek filters. everything works well

[Yi9569]

Requesting Changes

Both API endpoints worked as expected, however, I was able to retrieve information with the normal login token for http://localhost:4500/api/bm/materials/{projectId}. Please review if it were intentional.

[ezreal2020]

Tested n verified, works as expected

[one-community]

Thank you all, merging!