List function not working as intended

[Sean2110]

steps to replicate:

1. type "list 1"

even though i typed in a number after list, it still showed me the list. Instead, an error message should have been shown.

UG:

[nus-pe-bot]

[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

This is not a functionality issue, we have clearly mentioned that only list needs to be mentioned to view the list of photos or trips

The 'Original' Bug

[The team marked this bug as a duplicate of the following bug]

Help command does not pick out unexpected arguments

Help command will function normally even the user inputs arguments which is not part of expected usage of the program.

---

_{[original: nus-cs2113-AY2425S2/pe-interim#573] [original labels: severity.Low type.FunctionalityBug]}

Their Response to the 'Original' Bug

[This is the team's response to the above 'original' bug]

Here is what is mentioned in our UG:

This is not a functionality issue, we have clearly mentioned that only help needs to be mentioned to view the helper function details.

Items for the Tester to Verify

❓ Issue duplicate status

Team chose to mark this issue as a duplicate of another issue (as explained in the Team's response above)

• I disagree

Reason for disagreement: [replace this with your explanation]

---

❓ Issue response

Team chose [response.NotInScope]

• I disagree

Reason for disagreement: Thank you for your response! While I agree that it is not a functionality bug, it should have been changed to a feature flaw, i do not agree that this bug is not in scope.

From the CS2113 website:
Specificity of error message: Error messages can be correct but not specific enough (e.g., it says the input is 'invalid' without giving the reason, or gives too many possible reasons without pointing out the specific reason). These cases can be considered type.FeatureFlaw.

The program should not take in any other words other than the commands "help" or "list". After inputting extra words/numbers after the command, there is no error message being thrown to say that the command is invalid. Hence, it is a feature flaw that should have been corrected. It should not be not in scope.

for not in scope, this means:
How to prove that something is response.NotInScope: In general, a flaw (e.g., a missing feature, a suboptimal design of a feature, a known bug) can be considered NotInScope if rectifying it is less important than the work that has been done already (because it is fine to delay lower priority work until future iterations) i.e., the supposedly 'better' implementation will take more effort than the current implementation, reducing the effort available to spend on other more important tasks
In addition, the following (at least one) need to be satisfied:
The UG specifies it as not supported or coming in a future version.
The user cannot attempt to use the missing feature or when the user does so, the software fails gracefully, possibly with a suitable error message i.e., the software should not crash.

Correcting this bug is not less important nor is it mentioned in your UG that this bug is not supported/ is a planned implementation. This is obviously a bug. I would argue that it is of featureflaw.low instead of not in scope.

---