search

LWS49 / pe

0 stars 0 forks source link

Inconsistent behaviour when index is not valid #4

Open LWS49 opened 2 months ago

LWS49 commented 2 months ago

image.png When an index is used that is larger than the current number of clients in the list, instead of stating Invalid index, it raised the error that no prefix is supplied (when both are missing).

This is inconsistent behaviour, as when the index is negative (and therefore also invalid), the error message Invalid index appears.

image.png

Thus, the expected behaviour is that invalid indexes are raised with higher priority compared to missing prefixes. This should be the case for indexes that are too large as well. However, missing prefixes error is raised when using an index larger than the current number of clients.

soc-se-bot commented 2 months ago

Team's Response

The error message is not wrong, but it could be improved to be more consistent. It is a valid issue, but fixing it is less important than the work done in the current version of the product.

Items for the Tester to Verify

:question: Issue response

Team chose [response.NotInScope]

Reason for disagreement: [replace this with your explanation]