Inconsistent use of parameter attributes in various commands.

[Arnaxx54]

The put command requires the user to add n/ before entering the customers name. On the other hand, the history command does not require n/ before the customers name. It would be easier to make it consistent and always add n/ before the customers name. This will avoid constant lookup with the user guide.

[nus-se-script]

Team's Response

Thank you for the suggestion! We understand the value of consistency, but the current design is intentional. We decided to omit the prefix for the order parameter in the put command because we want to optimize speed and efficiency, especially given the high frequency of adding orders to customers in a fast-paced restaurant environment.

Items for the Tester to Verify

:question: Issue response

Team chose [response.Rejected]

• [x] I disagree

Reason for disagreement: Thank you for your feedback. I would like to clarify that my bug does not request for the addition of a prefix for an order parameter in the put command. Instead, it highlights the lack of consistency regarding /n prefix between different commands. Your response does not provide a relevant explanation for this error.

---