Open nus-se-script opened 1 week ago
Thank you for the suggestion. However, our team believes that the benefits of doing this does not outweigh the negatives.
As there are many possible invalid outputs with different errors, it will take a lot of space to show and explain them. Including such details would unnecessarily clutter the guide and detract from its main purpose of instructing users on how to use the application effectively.
Furthermore, our application provides clear and specific error messages directly to the user. User can easily correct their input according to the error message shown in the UI, so I think it's not necessary to duplicate this information in the User Guide.
--
Expected outputs when error occurs are not mentioned in the User Guide.
[original: nus-cs2103-AY2425S1/pe-interim#2188] [original labels: severity.Medium type.DocumentationBug]