Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Inconsistent error message for 'abort' commands. #2975

Open
nus-se-bot opened this issue Nov 12, 2021 · 1 comment
Open

Inconsistent error message for 'abort' commands. #2975

nus-se-bot opened this issue Nov 12, 2021 · 1 comment

Comments

@nus-se-bot
Copy link

nus-se-bot commented Nov 12, 2021

image.png

According to the user guide,
image.png

But abort/ and abort random behave differently. Even though I added additional character "WHITE_SPACErandom" after it.


[original: nus-cs2113-AY2122S1/pe-interim#2973] [original labels: severity.Low type.FunctionalityBug]
@KVignesh122
Copy link
Contributor

KVignesh122 commented Nov 14, 2021

Team's Response

In the main workspace, the one word "abort/" (without any spaces) is considered a command keyword by itself and since there are no other possible command keywords correlating to this input, this command is invalid and the program does not understand it.

However, when inputing "abort random", "abort" is interpreted as a keyword and the " random" is interpreted as an extraneous parameter. We had already merntioned in UG that all extraneous commands will be ignored:

image.png

So, the input "abort random" is interpreted as "abort" but since "abort" is only possible in the edit/add processes:

image.png

In the main workspace, the "abort" command returns an accurate error message.

This is a duplicate of issue #2907 as the problem lies in not following the UG instructions carefully which explains how extraneous parameters are handled.

Duplicate status (if any):

Duplicate of #2907

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants