Open meowwtama opened 6 months ago
To address the first concern that users have to scroll to the end, the remove
command actually works in a filtered list, which is achieved when used in conjunction with the find
command, as indicated in the tip here:
The first concern is hence not a bug.
For the second concern about "The error message stating an index is invalid is vague as it does not tell us why, in this case 3, is invalid as it is a positive index.", it is actually more of a feature flaw (not functionality bug - which means product does not work as expected), but it is a feature flaw that is not in scope.
According to the UG, we have also specified what an index is, and with the current differentiated error message, it is distinguishable and doesn't bring great inconvenience to users when using it.
Feature flaw justification:
Not In Scope justification:
The improved error messages can be delayed to further iterations, because as seen above, it does not bring inconvenience or ambiguity to users. Furthermore, current app does not crash and is still working fine. Thus we feel that this is Not In Scope, hope this clarifies! Thank you
Team chose [response.NotInScope
]
Reason for disagreement: [replace this with your explanation]
In the context of a large address book, the last index of the contact would be hard to find as users would have to scroll to the end.
The error message stating an index is invalid is vague as it does not tell us why, in this case 3, is invalid as it is a positive index. Should state that index is out of range or smth like that.