feat(backend): Implement Grade Data Management API Endpoints

[TKanX]

Summary:

Implemented a comprehensive grade data management system with the following features:

• Semester-level Hierarchical Data Management: Manage terms, courses, categories, and tasks.
• Basic Academic Data Calculations: Calculate total scores and GPA.
• Import/Export Functionality: Import and export academic data easily.
• User Settings Integration: Seamless integration with user settings for efficient data management.

Changes:

1. Added Backend API Endpoints:

   • Create Semester:
     • POST /grades: Create a new semester with basic details.
   • Get All Semesters:
     • GET /grades: Fetch a list of semesters with basic details.
   • Get Semester Details:
     • GET /grades/:id: Fetch detailed data for a specific semester, including nested courses, categories, and tasks.
   • Update Semester Data:
     • PUT /grades/:id: Replace all data for a specific semester, including courses, categories, and tasks.
   • Partial Update of Semester Data:
     • PATCH /grades/:id: Apply JSON Patch updates to specific elements within a semester.
   • Delete Semester:
     • DELETE /grades/:id: Delete a specific semester by ID.
   • Export Specific Semester Data:
     • GET /grades/:id/export: Export detailed data of a specific semester as a JSON file.
   • Export All Semesters Data:
     • GET /grades/export: Export all semesters' data as a JSON file.
   • Import Semester Data:
     • POST /grades/import: Bulk import multiple semesters with nested data (courses, categories, tasks).

2. Model and Schema Changes:

   • Added a Grade schema to the MongoDB database for managing semester-level data.
   • Added indexes for startDate and endDate in the Grade schema.
   • Enhanced the Grade schema to include timestamps and an optional extraCredit field.
   • Added optional goal fields to the Grade and Course schemas, and a goals field to the User schema with GPA and weight goals.
   • Set default values for roles and locked fields, and ensured proper indexing for query performance.

3. Utility Enhancements:

   • Added validation functions for grade name, username, and school name maximum length.
   • Added validation functions for start and end dates.
   • Improved GPA goal validation to ensure non-negative values.

4. Documentation Updates:

   • Updated API.md to include detailed descriptions and example requests/responses for all new grade endpoints.
   • Updated the README to include customizable grade modes and grade management functionality.

5. Frontend Enhancements:

   • Added GPA goals input fields and updated settings components to handle GPA goals.

[Copilot]

Copilot reviewed 7 out of 12 changed files in this pull request and generated 4 comments.

Files not reviewed (5)

• frontend/src/views/pages/user/settings.ejs: Language not supported
• README.md: Evaluated as low risk
• backend/src/controllers/authControllers.js: Evaluated as low risk
• backend/src/routes/index.js: Evaluated as low risk
• backend/src/controllers/userControllers.js: Evaluated as low risk

Copilot reviewed 7 out of 12 changed files in this pull request and generated no comments.

Files not reviewed (5)

• frontend/src/views/pages/user/settings.ejs: Language not supported
• backend/src/services/gradeService.js: Evaluated as low risk
• README.md: Evaluated as low risk
• backend/src/routes/index.js: Evaluated as low risk
• backend/src/controllers/authControllers.js: Evaluated as low risk

Comments suppressed due to low confidence (5)

backend/src/models/gradeSchema.js:149

• The 'percentage' field should have a validation to ensure it falls within a valid range (e.g., 0 to 100).

percentage: { type: Number, required: true, },

backend/src/models/gradeSchema.js:154

• The 'letter' field should have a validation to ensure it matches valid letter grades (e.g., A, B, C, etc.).

letter: { type: String, required: true, },

backend/src/models/gradeSchema.js:158

• The 'GPA' field should have a maximum value validation (e.g., 4.0 for standard GPA).

GPA: { type: Number, required: true, min: 0, },

backend/src/models/gradeSchema.js:163

• The 'honorsGPA' field should have a maximum value validation.

honorsGPA: { type: Number, required: true, min: 0, },

backend/src/models/gradeSchema.js:168

• The 'advancedGPA' field should have a maximum value validation.

advancedGPA: { type: Number, required: true, min: 0, },