Open ChewyChair opened 2 years ago
No details provided by team.
[The team marked this bug as a duplicate of the following bug]
Running the module command alone shows error
Command:
module
Running
module
throws an uncaught exception.Perhaps the exception should be caught and an appropriate error message can be shown
[original: nus-cs2113-AY2122S1/pe-interim#572] [original labels: severity.High type.FunctionalityBug]
[This is the team's response to the above 'original' bug]
Severity changed to Low: This only happens rarely and in exceptional circumstances, i.e. when the user fails to refer to the UG and help before attempting to use the command. Moreover, even average users can sense that something is wrong and will naturally refer to the documentation for help. It as well does not terminate or affect the program in any way other than printing a relatively cryptic error message.
Type changed to FeatureFlaw: it is a good to have but not present feature, not a malfunctioning existing one.
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]
Typing the
module
command with no other arguments does not print a useful message like the other commands. Perhaps it can be added.