Open ryantianj opened 3 years ago
In this issue, there are two errors that are being parsed for:
We chose to parse for error 1 before error 2. The same issue would have surfaced if we chose to parse error 2 first before error 1. Hence we reject this bug.
Team chose [response.Rejected
]
Reason for disagreement: As mentioned about the two issues, I believe parsing 2 before 1 is different and would result in lesser inconvenience for the user: Based on current implementation, If the user has erroneous inputs in all of the fields, the user has to correct all the errors in the fields one-by-one before the app informs the user that the contact is a duplicate. Parsing 2 before 1, User will be immediately informed that it is a duplicate contact. The correctness of the handle/inputs would not have mattered if it was duplicate.
Adding a duplicate contact with an invalid handle results in the error below:
As a user, i would have expected this error instead: