Open wengkit1 opened 1 year ago
Thanks for the bug report. However in our implementation, the check for start time before end time happens within the ParserUtil
class (when the constructor of TimeSlot
is called by ParserUtil
with a timeslot string, it calls checkArgument(startingDateTime.isBefore(endingDateTime), MESSAGE_START_AFTER_END)
to ensure this). Since this is an implementation detail of the ParserUtil
class, it is common to any appointment-related command, and we omitted this low level detail from the sequence diagram for AddAppointmentCommand
.
Team chose [response.Rejected
]
Reason for disagreement: The purpose of highlighting both sequence diagrams, is to show that ParserUtil is not referenced by either. Since this constraint is unique to your app, I hope you can understand from your own explanation, how this might be confusing to some.
Start time before end time predicate missing from sequence.
It should be mentioned in sequence, as the code checks for start time before end time before an appointment is added.