Expense logging issue

[sxkhoo]

Expense still logged despite writing log expense twice.

[nus-pe-script]

[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]

Team's Response

It doesn't affect user expense (log-expense still can function properly). We intended our commands to work like that (ignoring duplicating the main word of command)

Items for the Tester to Verify

❓ Issue response

Team chose [response.Rejected]

• I disagree

Reason for disagreement: While the command may technically execute successfully, accepting duplicated main keywords like log-expense log-expense reflects unexpected behavior from a user perspective. This leniency in input parsing can cause confusion, especially if users make accidental repetitions due to lag or typing errors.

In most command-line interfaces, commands are expected to follow a strict and predictable syntax. Allowing malformed or duplicated inputs to proceed without error undermines this principle and can lead to unintentional expense logging or reduced user confidence in the system.

Even if it doesn’t currently affect the core functionality, this issue indicates a lack of input validation and could introduce edge-case bugs in the future. A simple check to reject or warn against duplicated command keywords would improve robustness and align the system with common user expectations.

Therefore, I believe this issue should not be rejected but I agree that severity can be reduced to Low instead.

---

❓ Issue severity

Team chose [severity.Low]
Originally [severity.Medium]

• I disagree

Reason for disagreement: [replace this with your explanation]

---