Open vishnuvk47 opened 1 year ago
Deals with the ordering of flags. Also, UG already states the correct ordering of the format.
[The team marked this bug as a duplicate of the following bug]
Incorrect output when input is in wrong order happens with list command as well
Should be handled as an exception or input be read as appropriate using flags
[original: nus-cs2113-AY2223S2/pe-interim#1260] [original labels: type.FunctionalityBug severity.Low]
[This is the team's response to the above 'original' bug]
Should be a featureflaw as it deals with the order of the flags.
Severity should be low as it only appears in rare situations when a user does not follow the intended formatting. It does not affect the normal operations according to the tester's bug report.
Items for the Tester to Verify
:question: Issue duplicate status
Team chose to mark this issue as a duplicate of another issue (as explained in the Team's response above)
Reason for disagreement: conditions to mark under duplicate:
(a): With regard to point a, this is definitely not the EXACT same bug as it happens for a different command.
(b): See below for teams code on how parser is implemented, each command has its own method where the relevant parsing is done; hence, solving one doesn't resolve all the others as they will need to make changes to all the other methods as well.
Change order of parameter should throw error or handle the inputs as appropriate as flags were used, instead of following through with wrong output