nus-se-bot
commented
1 year ago Team's Response
The standard behaviour is that multiple parameters are provided, we take the last value provided.
Unless there is a deviation, for example for note/, we have it specified in the info box at the start of each command.
If the user read the last bullet point of the info box above, the user will know that the command handles repeated parameters. Thus, the user does not have to execute any commands to "discover" that it does not handle repeated parameters
Items for the Tester to Verify
:question: Issue response
Team chose [response.Rejected]
- [x] I disagree
Reason for disagreement: A 'very low' severity might be more suitable in this case since the issue is that the details on which commands are capable of handling repeated parameters is not clearly presented in the same place where the user is first notified of it but instead spread throughout the UG.
In most commands, if the same parameter is repeated and only one is required, we take the last value provided.
-> It is not clear from this note in the UG which commands are capable of handling repeated parameters and which ones aren't. So the user will only discover a command does not handle repeated parameters after executing a command which might be undesirable.