search

nus-cs2103-AY2122S1 / pe-dev-response

0 stars 0 forks source link

Command prefixes are unnecessarily case-sensitive #5593

Open nus-se-bot opened 2 years ago

nus-se-bot commented 2 years ago

Prefixes for commands need not be case-sensitive. Feels to be unnecessary input-validation. Case-insensitive prefixes would be more user-friendly, as it does not seem like there is currently a need for case-sensitiveness. Future prefixes could easily be created to be unique content-wise compared to existing prefixes.

image.png

Could be medium severity if user is not tech-savvy.

[original: nus-cs2103-AY2122S1/pe-interim#5616] [original labels: severity.Low type.FeatureFlaw]

yeppog commented 2 years ago

Team's Response

Future prefixes could easily be created to be unique content-wise compared to existing prefixes.

I believe allowing for case flexibility restricts us in the number of possible prefixes that could be used in the future. If the application scale up and we end up having a large amount of commands, starting from a point where it is case inflexible makes it detrimental to the user. In the case we need to revert to a case-inflexible system of prefixes to accommodate more prefixes, it would be a nightmare to the user to switch.

Furthermore, it doesn't seem like a chore to the users using CLI. Compare it to using flag args in the command line for applications. flags (similar to prefixes in this case) are meant to be case sensitive. Try running git reset --soft vs git reset --SOFT. The one with caps would give you an error showing that it is not recognised.

Hence, we believe this behavior is justified.

Duplicate status (if any):

--