Currently, we are only assigning the score for each student (10 points for easy, 20 for medium and 30 for hard). However, we would like to also add the number of easy, medium and hard issues that students solve to the leaderboard API response. After this, the API response should look something like this:

{
...
  "username": {
    "name": "name",
    "rollNumber": "2020XXX-YYY",
    "score": S,
    "easy": E,
    "medium": M,
    "hard": H,
  },
...
}

The score calculation logic is here

This issue is fairly simple to solve given that the checks for easy, medium and hard issues are already present.

Create a Readme similar to the frontend repo of this website (https://github.com/aaryak-shah/git-init-FOSS).

Things to note:

1. Local setup steps may differ
2. Features are to be added accordingly
3. This server has a cron job built-in which run every 1 hour and updates the scores of participants in score.json file, which is then served using a single endpoint to the frontend. Try including about the cron job in the README. Also you can read more about crontab and how it can be used to run the cron job locally using script.cron file.

@kunaljain0212 after the addition of third screen (i.e. statistics) can I update the readme file

Instead of using objects for projects & students we can store them in a csv file and import them wherever required as json object using csvtojson

Add an endpoint to the server, say /stats that will return the current statistics of the event in a desired format. This issue is a precursor to aaryak-shah/git-init-FOSS#20 and so the format of the stats should be what the frontend can use effectively.

Stats to be found, with respect to the event-registered repos:

• Total number of PRs
• Nuber of easy, medium, hard PRs
• Number of active contributors (i.e. those who have at least one succesfully merged PR)
  + Any additional stats you think are suitable

At the moment, the code formatting and code style are inconsistent throughout the project. This can be easily fixed by using ESLint, and configuring it to use the Prettier plugin. Here's a useful guide for configuring ESLint with Prettier.

Additionally, add a lint script to check the linting, and a lint:fix script to automatically fix linting issues in the package.json.