Open kervyntan opened 5 months ago
[IMPORTANT!: Please do not edit or reply to this comment using the GitHub UI. You can respond to it using CATcher during the next phase of the PE]
Thank you for your bug report. However, the error message might be from your input instead.
The following screen shot shows the result if the input is reschedule 1 mr/n e/02-02-2025T15:00 s/02-02-2025T10:00
.
Team chose [response.Rejected
]
Reason for disagreement: [replace this with your reason]
Description
User Guide states that parameters can be passed in any order for the commands. However, after testing, schedule and reschedule commands can only be successfully interpreted by the application if they are keyed in in the manner specified.
Steps to reproduce
Launch the application for the first time to load initial data.
Run
schedule ..
orreschedule ..
commands with parameters in different order than what specified in the user guide i.e. swap s/ e/ parameters for example.Expected behaviour
According to the User Guide, swapping the parameters around should still result in a successful command being entered.
Actual behaviour
Command fails to be entered, error message thrown to the user.