Open boonhaii opened 2 years ago
With regards to the specificity of the error message: it is correct and specific enough as it does tell you what the invalid input is (i.e an index) instead of just mentioning that the command is invalid.
Furthermore, there are only 2 indexes to choose from - the tutee index and the lesson index, and the definition of integer is not as ambiguous for users to wonder if the tutee index 1
is being referred to as invalid here.
Team chose [response.Rejected
]
Reason for disagreement: This error message was raised as a bug exactly because it is not explicitly stated which index the error message is referring to. The user may believe that the error message is corresponding to the person index rather than the lesson index which is missing value here and the source of error. This would may cause the user to believe that there is a FunctionalityBug when the application is actually working correctly. Thus, I believe that this bug should be valid and the error message given should be more specific on the Index it is referring to.
Team chose [type.FeatureFlaw
]
Originally [type.FunctionalityBug
]
Reason for disagreement: [replace this with your explanation]
Team chose [severity.VeryLow
]
Originally [severity.Low
]
Reason for disagreement: This issue should not be of type severity.VeryLow as it is not a purely cosmetic issue. The severity is of type severity.Low as while it may be common, the error message still indicates the error, albeit insufficiently specific. Thus, I believe that it is only in rare cases that the user may not be able to solve the issue easily with the current error message provided.
When the command
payment 1 lesson/
is input into the application, the error message "Index is not a non-zero unsigned integer" is returned. However, while I understand the index refers to the lesson index, other users may mistake it for the student index.