Skip to content

Commit

Permalink
Update DeveloperGuide.md
Browse files Browse the repository at this point in the history 
Updated Planned enhancements
  • Loading branch information
@WinstonLeonard
WinstonLeonard committed Nov 14, 2023
1 parent 03ecfc5 commit 47e967e
Showing 1 changed file with 7 additions and 4 deletions.
11 changes: 7 additions & 4 deletions docs/DeveloperGuide.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -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.
Expand Down Expand Up @@ -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.

0 comments on commit 47e967e

Please sign in to comment.