Open UdhayaShan1 opened 2 months ago
We believe this shouldn't be an issue. The current implementation helps the user to fix the errors one by one. For your case fixing the p/PHONE
field will result in the error message subsequently tell you that the e/EMAIL
field is wrong in which you then can proceed to fix it.
Team chose [response.Rejected
]
Reason for disagreement: To reject this issue means the current implementation is expected and correct behaviour and not acknowledging my issue's merit.
I will give concession if this documented in any way, but this explanation "The current implementation helps the user to fix the errors one by one." is the first time I am seeing it, which is not in the UG and product.
Furthermore, I believe my issue is an FeatureFlaw
as we are unable to see what the errors are and we have a generic (incomplete) error that only shows error for just one field.
I expect something like
Which is reasonable for a CLI command based application that should tell the user what fields they can fix instead of one-by-one fixing and seeing one-by-one which fields are wrong.
Since there is possible room for improvement to fix this generic command error message, I do not think this should be rejected.
add n/wdadad p/9021 5365 e/ud+-@gmail.com
has two wrong fieldsEmail should not have consecutive symbols and number should not have spaces.
However, system replies just![image.png](https://raw.githubusercontent.com/UdhayaShan1/pe/main/files/c277d68d-ae95-412f-aa4e-a50d1e102460.png)
It should show all errors present so we are able to rectify, here I should also see a error message for email field hence making the current error rather generic.