Non-Numeric `paid` Field Returns Unhelpful Exception

[e1121208]

Description

The paid/ field should be numerical is not alerted to the user.

---

Steps to Reproduce

1. Attempt adding a user with the paid/ field storing non-numeric values.
2. Observe that the result display returned does not address the issue.

Expected Behavior

Users should be prompted of the strictly numeric paid field when inputting a non-numeric paid/.

Actual Behavior

However, the result display only reminds user that the decimal place should be at most two and within the price range specified by the program.

Additional Information

Input:
add n/John Doe p/98765432 e/johnd@example.com a/311, Clementi Ave 2, #02-25 t/Sunday-1000-1200 s/Biology r/900 paid/lll owed/3000
Output:

---

Suggested Improvement

Consider throwing another command exception in the case of that field being non-numeric.

[nus-se-script]

Team's Response

Thank you for your input. We felt that this is of a lower priority than what we have done in v1.6.

We felt that our help message is quite specific to tell user what is an acceptable input for our paid/ field.
Moreover, the PaidAmount also implies to the user that the input for the field should be an amount, i.e. a numeric value.
When we think in the user's perspective, upon seeing the message
PaidAmount should ...
and
1. at most 2 decimal places
and
2. is between the range of ...

we felt that the user should be able to understand quite clearly that the input is a numeric value.

Of course, your suggestion is valuable to our team in terms of improving the user experience for UGTeach, and we will consider improving this in the future iteration, by adding another line telling user that it should be strictly numeric.

Items for the Tester to Verify

❓ Issue response

Team chose [response.NotInScope]

• I disagree

Reason for disagreement: [replace this with your explanation]

---