Due Dates

[IsoPhoenix]

Due Dates

Overview

Enforce due dates on tasks. Tasks should expire and no longer be completable past the due date

Frontend

• Display students' expired tasks in the Overdue tab in Student View Main Page (see "Student View Main Page" frame in Figma)
• Display students' expired tasks in the student modal in class page, teacher view.
  • There's an existing table with the completed tasks. You can add an [MUI Tab group](https://mui.com/material-ui/react-tabs/) to toggle between these two tables

Backend

• To be clever about due date enforcement, we need to check for due date expiry whenever a student's tasks are loaded. This occurs twice: Student View main page and Teacher View class page (opening the student's modal).
• Write a function in mutations.js that given an array of task IDs and a player ID, will remove the player ID from the assigned array and add it to the expired array for every task
• Use the useEffect() hook to implement due date checking when a student loads a classroom (in Main.js) and when a teaher opens the modal that will show a student's completed tasks (ClassTeacherModal.js).
  • Logic:
    1. Fetch the student's assigned tasks
    2. For each task, if the current time (now()) is past the due date, append the task ID to a temp array
    3. Pass this temp array into the mutation you wrote earlier
  • The student's assigned tasks should already be fetched for display in the existing code. You can utilize this existing array for the above logic, but be careful because updating the tasks collection in the onSnapshot() call for the tasks collection may cause an infinite loop. To be efficient with code and avoid writing another onSnapshot just for due date checking, you will need to be smart/careful about how you use state variables, onSnapshot(), useEffect(), and possibly async functions. If you are unsure about this let me know so I can help you out.
• When fetching task data for a student to display tasks (whether for the overdue tab or for the class interface modal), you shouldn't need to write more than one onSnapshot() call. Write one call for all the tasks in the classroom and then sort the result using Javascript to categorize various tasks (All Quests, Requested, Confirmed, Overdue). (This means you may need to modify existing onSnapshot calls if they do not ask for enough).

[IsoPhoenix]

Addendum for functionality when teacher edits a task by changing the due date:

When a teacher edits the due date of a task: If the new due date is in the future, you should transfer all player IDs from the expired array back to the assigned array. This covers retroactive action of a teacher giving an "extension" by changing due date.

This functionality should happen when the task is actually edited (i.e. do the checking and/or moving when the edit is confirmed, not when the due date is just being changed in the edit modal).