From 47e967e948e9a600f7fce24f6e0fb6adf236cc2b Mon Sep 17 00:00:00 2001 From: Winston Date: Tue, 14 Nov 2023 10:42:48 +0800 Subject: [PATCH] Update DeveloperGuide.md Updated Planned enhancements --- docs/DeveloperGuide.md | 11 +++++++---- 1 file changed, 7 insertions(+), 4 deletions(-) diff --git a/docs/DeveloperGuide.md b/docs/DeveloperGuide.md index 18a174c35b5..49ead4aa6b8 100644 --- a/docs/DeveloperGuide.md +++ b/docs/DeveloperGuide.md @@ -995,10 +995,6 @@ testers are expected to do more *exploratory* testing. ## **Planned Enhancements** -1. To be able to group/tag tutees into "Tutor Groups". These tutees will be able to have the same timeslot if they belong to the same "Tutor Group" -2. Allow tutees to have multiple lessons. Our current implementation does not allow the same tutee to have multiple lesson as a tutee is uniquely identified by their name and phone number. For example, if the user is teaching John Maths on Monday, he can't teach John Physics on a different day because the system will identify John as a duplicate tutee. -3. Enhance the edit feature. Currently, our edit feature might result in a bug if the NAME and (DAY/BEGIN/END) fields are edited at the same time. For example, if tutee index 1 has the name John and has a lesson on Monday 20:00 - 21:00, trying to do `edit 1 n/Doe end/2030` will result in an error (throwing the message that this date clashes with an existing scheduke). - ### Batch Processing for Paid Command Reason: This enhancement allows users to mark multiple persons as paid in a single command, improving efficiency. @@ -1042,4 +1038,11 @@ would allow for more flexibility in the application. Idea: Create a `GroupTag` field for `Lesson` class which contain an ID for each `Lesson` object if they are group lessons. When checking if two lesson clashes, allow for lesson clash if `Lesson` objects have the same IDs which means they are the same group lesson. +### Enhance Edit Feature +Reason: Currently, the edit feature might result in a bug if the NAME and (DAY/BEGIN/END) fields are edited at the same time. +For example, if tutee index 1 has the name John and has a lesson on Monday 20:00 - 21:00, trying to do `edit 1 n/Doe end/2030` +will result in an error (throwing the message that this date clashes with an existing schedule). This is because it considers the +pre-edited tutee as a schedule clash. +Idea: Have an additional check with the index. If the edited person has the same index as the pre-edited person, then the +system should allow the edit to happen.