nus-pe-bot
commented
3 years ago Team's Response
No response provided.
The 'Original' Bug
[The team marked this bug as a duplicate of the following bug]
Inconsistent error messages
Steps to reproduce: odel 12121212 odel 121212121212
Expected: Similar error that the index is not in range
Actual: One specifies that the index is invalid, another specifies that the command format is incorrect. However, following the error message provided, a INDEX param was provided and it is positive.
[original: nus-cs2103-AY2021S2/pe-interim#2799] [original labels: severity.Medium type.FunctionalityBug]
Their Response to the 'Original' Bug
[This is the team's response to the above 'original' bug]
Severity justification: Does not affect the normal operation of the app, may be an issue in some rare situations. Duplicate justification: Similar inconsistencies are shown as the underlying implementation of index is int instead of BigInteger. They can all be addressed by changing this implementation.
Items for the Tester to Verify
:question: Issue duplicate status
Team chose to mark this issue as a duplicate of another issue (as explained in the Team's response above)
- [ ] I disagree
Reason for disagreement: [replace this with your explanation]
:question: Issue severity
Team chose [severity.Low]
Originally [severity.Medium]
- [ ] I disagree
Reason for disagreement: [replace this with your explanation]
Constraint provided states any positive integer is allowed for Index (e.g. rdel INDEX, redit INDEX), however when inputting a number presumably greater than the Integer Limit for Java, an error message is returned that does not identify the issue.