Context : 2024-01-01 12:00 Appointment for John Doe already exists in the current list of reminders
Inputted command :
ra n/John dt/2024-01-01 12:00 d/appointment
Expected behaviour : Unable to add this reminder for John Doe as it is a duplicate reminder.
Actual behaviour : A new reminder section is added for John Doe, even though it is the same thing.
Suggested solution : Make the description for reminders case insensitive so as to avoid duplicate reminders from being added into the reminder list. This can prevent the overcrowding of the reminder list if users accidentally input duplicate reminders for the same person.
Currently, the REMINDER_DESCRIPTION can take in any inputs and it was kept that way to provide users the freedom to tailor reminders to their needs.
We allow this because we do not want to be overzealous in checking for duplicate reminders.
Therefore, it is not a functionality bug but a deliberate design choice that trusts the users to make their own choices on what they want to include, allowing the user greater flexibility.
Context : 2024-01-01 12:00 Appointment for John Doe already exists in the current list of reminders
Inputted command :
ra n/John dt/2024-01-01 12:00 d/appointment
Expected behaviour : Unable to add this reminder for John Doe as it is a duplicate reminder.
Actual behaviour : A new reminder section is added for John Doe, even though it is the same thing.
Suggested solution : Make the description for reminders case insensitive so as to avoid duplicate reminders from being added into the reminder list. This can prevent the overcrowding of the reminder list if users accidentally input duplicate reminders for the same person.
[original: nus-cs2103-AY2425S1/pe-interim#565] [original labels: severity.Medium type.FunctionalityBug]