Updated the projectController.js file to make the necessary modifications as mentioned in issue #98

[ritankarsaha]

Fixes #98
Modified the projectController.js file to make the necessary modifications and ensure the robustness, maintainability and readability of the code.

Description

-Header Extraction: Common headers are extracted to avoid repetition.
-Promise.allSettled: This allows continuing if some API calls fail.
-map Simplification: Instead of copying unnecessary data, it retrieves essential repository details.
-Fallbacks for Optional Fields: Added default values for description, open_issues_count, and stargazers_count for missing data.

The screenshot shows that the webpage works properly and takes load correctly after all the changes.

Screen.Recording.2024-11-03.at.2.22.57.PM.mov

The screen recording shows that the webpage remains unaffected and works properly, fetches data properly after all the changes that has been made

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• [x ] New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

• [x ] My code follows the code style of this project.
• My change requires a change to the documentation.
• I have updated the documentation accordingly.
• [x ] All new and existing tests have passed and it does not give any unexpected error for the same.

[rajutkarsh07]

@ritankarsaha fix the CI for the backend it is failing

[ritankarsaha]

@ritankarsaha fix the CI for the backend it is failing

Yeah will fix this and push a new commit into the PR. Thanks

[ritankarsaha]

@rajutkarsh07 Made the necessary modifications and pushed a new commit into the PR.

The CI error occurs because the GITHUB_ACCESS_TOKEN is not defined in the environment during the test run.

I can Update your projectController.js to allow tests to run without requiring a real GITHUB_ACCESS_TOKEN.

const axios = require('axios');
const accessToken = process.env.GITHUB_ACCESS_TOKEN || 'test-token'; // Fallback for tests

if (process.env.NODE_ENV !== 'test' && !accessToken) {
  throw new Error("GITHUB_ACCESS_TOKEN is not defined in the environment.");
}

const GITHUB_API_URL = 'https://api.github.com';
const headers = {
  Authorization: `token ${accessToken}`,
};

This allows tests to run in the test environment without requiring a real token.
Should I do this and push the changes ? or let it as it be ? , because including this would i guess bring down the code quality un-necessarily.

[rajutkarsh07]

if adding this will fix the CI then add this line