Open siqirua opened 9 months ago
According to the UG, the error message is expected to be "The person index provided is
invalid" since it is not within the range and it is an integer, but in fact it returns "Invalid command format!" when the index is 0.
It was mentioned in the UG that the error message “Invalid command format! …” will be issued when the index is not correctly specified as an integer.
We have also defined index under the fields table where it is specified to be a positive integer of the range (1, 2, 3, …, 2147483647).
Additionally, we also have a planned enhancement regarding command-specific error messages. Hence we plan to be able to receive the command of “dp 0” and give a more accurate error message “The index should be a positive integer.”
Team chose [response.NotInScope
]
Reason for disagreement: From what I understand from your DG Planned Enhancement, what you meant by command-specific error message is to explain the error message under the context of a specific command. However, this bug is due to a misclassification of the error, which I believe should not be considered in 'Not In Scope'.
(Other reason you may refer to the explanation below for the severity)