nus-se-script
commented
1 week ago Team's Response
The team does not believe that the difference in the command formats in their respective headers should be considered a bug.
The addition of flags within the command headers, such as in catalog and view, are necessary to differentiate between their respective variations, which are similar in format, such as catalog -a vs catalog -a -m and view vs view -b -s as examples, which ultimately serve to improve clarity through greater specificity and details that is more immediate to the reader.
The same rationale/argument can be used to explain the lack of flags in other commands like sales/schedule due to fact that there is only one variation for each of them thus the addition of flags would not have served any additional purpose of differentiation or enhancing clarity. Additionally, the full command format for both commands, flags included, follows immediately after the heading and there is no ambiguity in its usage as a result.
Ultimately, the team believes the tester's argument is not valid, as the use of flags for commands with multiple similar variations is intentional to distinguish between them, while the absence of flags for commands with only one variation helps maintain clarity. Therefore, what was described as an 'inconsistency' actually serves to improve differentiation and ensure ease of understanding.
Items for the Tester to Verify
:question: Issue response
Team chose [response.Rejected]
- [ ] I disagree
Reason for disagreement: [replace this with your explanation]
Image 1:
Image 2:
In Image 1, the command options are given in the description of the command. However, the same is not done for the command in Image 2. Perhaps more consistency can be provided in the UG to improve its clarity.