Open david-eom opened 3 years ago
No details provided by team.
[The team marked this bug as a duplicate of the following bug]
Incorrect exception thrown for index 0
To reproduce:
- type
clear
to purge the databse- type
editLink 1 n/asdf
, the errorThe link index provided is invalid
pops up- type
editLink 0 n/asdf
, we would expect the same error. But instead the errorInvalid command format
is being thrown.This bug persists for all index based commands.
For non-zero indexes:
For zero indexes:
[original: nus-cs2103-AY2122S1/pe-interim#2933] [original labels: severity.Low type.FunctionalityBug]
[This is the team's response to the above 'original' bug]
We only accept integers between 1 and 2147483647 for the index, which is indicated in the error message. In both the UG and the app itself, a command with an index out of the range is defined as having invalid format.
Team chose to mark this issue as a duplicate of another issue (as explained in the Team's response above)
Reason for disagreement: [replace this with your explanation]
Team chose [response.Rejected
]
Reason for disagreement: [replace this with your explanation]
Team chose [severity.VeryLow
]
Originally [severity.Low
]
Reason for disagreement: [replace this with your explanation]
When we type in
editTask 2147483647 n/CS2105 Assg 3
in the window, it says "The task index provided is invalid". Normally we would expect the same exception to be thrown foreditTask 2147483648 n/CS2105 Assg 3
as we only incremented the index by one.However, when we do type in
editTask 2147483648 n/CS2105 Assg 3
, a it shows invalid command format when the format is actually valid, just that the index is too big.This shows that ManageMe did not handle Integer.maxint value properly in its parser implementation. A user might get confused for this.
The same error persists for all INDEX based commands e.g. editMod, editTask and so on.