search

kirangeofran / pe

0 stars 0 forks source link

Inability to handle lack of blankspaces in between inputs #6

Open kirangeofran opened 4 months ago

kirangeofran commented 4 months ago

The system is unable to detect the commands if you remove the blankspaces in between each flag in the command. For example, if you remove the space in front of -q in the first picture or you remove the space in between -e and the arguments in the second picture. It would be more user-friendly if you were able to parse out the inputs by detecting the flags even if there is no blankspaces in between.

image.png

image.png

soc-pe-bot commented 4 months ago

Team's Response

Thanks for raising this encounter you had with MediTracker.

We believe that we have already specified in our UG, to follow the commands accordingly. Even though your suggestion is great, we believe that following our command provided would be the most valid action to take as we have already specify to the user which flags or arguments they are missing.

Since our flags starts with a hyphen, it only adds unnecessary complexity to the processing of the parameters and is not worth our time to address that.

We also believe the severity is low since we cannot possible pre-empt where the user will use the hyphens. Some usage may be as intended (like ice-cream, pre-emption) and missing spaces are mostly typos which can be easily handled by the end user.

Items for the Tester to Verify

:question: Issue response

Team chose [response.NotInScope]

Reason for disagreement: I feel that a good cli app should be able to take in spaces. If not , it would hinder the usage of the app. However, I agree that the severity should be lower so I have accepted the drop in severity to Low from Medium.

## :question: Issue severity Team chose [`severity.Low`] Originally [`severity.Medium`] - [ ] I disagree **Reason for disagreement:** [replace this with your explanation]