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

Group-related commands are hard to type #2

Open
ncduy0303 opened this issue Nov 17, 2023 · 1 comment
Open

Group-related commands are hard to type #2

ncduy0303 opened this issue Nov 17, 2023 · 1 comment

Comments

@ncduy0303
Copy link
Owner

ncduy0303 commented Nov 17, 2023

Description

Using group-related commands such as deleteGroup, findGroup, etc.

Expected behaviour

It should be short and not in capital-case

Actual behaviour

It is long and has a capital G which causes more time to type

Reason for severity

Small inconvenience for users

@nus-pe-script
Copy link

nus-pe-script commented Nov 20, 2023

Team's Response

We do not believe this is a bug as we believe this is not an inconvenience and as students(who know how to code), using camelCase would not be a problem.

Items for the Tester to Verify

❓ Issue response

Team chose [response.Rejected]

  • I disagree

Reason for disagreement: As mentioned in the course website, the application is expected to be optimised for CLI usage, so unnecessary long and complicated command format is supposed to be a feature flaw.

LongCommandFeatureFlaw.png

I believe the length and case-sensitivity of these commands is unneccessary (causing additional keystrokes) when the case-insensitive version suffices (all lowercase commands and the command keyword can also be shorter such as findgroup or maybe even fg which is similar to common unix CLI commands such as cd and ls) for these commands:

  • listGroup
  • deleteGroup
  • findGroup
  • filterGroup
  • checkGroup

As I think these commands are not used frequently compared to Person related commands, it can cause minor inconvenience for usage in rare situations and thus should be a valid FeatureFlaw with Low severity.


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

2 participants