`PREFIX` case sensitive

[UdhayaShan1]

add N/Denzel p/92015365 e/ud@gmail.com

This sould be valid as N is just the caps of n, hence I expect the command to run.

[nus-se-bot]

Team's Response

Hi thanks for the catch but we believe this should be of no hindrance to the user but more of preference and cosmetics.

Items for the Tester to Verify

:question: Issue response

Team chose [response.NotInScope]

• [x] I disagree

Reason for disagreement: I disagree purely on basis of team's response. This causes some hindrance to user on basis of strict case sensitivity. Also, there is no justification provided in UG why this was allowed or if the effort spent to fix this is not worthwhile.

• This is also overzealous validation of my prefixes, suppose a user has CAPS on and types all prefixes as caps add N/DENZEL E/EMAIL... he has to go back and change all of these prefixes to non capitalized one by one. He should expect N/ to be the same n/ which is expected behaviour of any CLI application.

• Also preference is mentioned, if it is about preference, the application should allow for case-insensitivity if anything.

• Cosmetics is also mentioned, this is not about cosmetics but a possible feature flaw.

• Apart from their explanation, notInScope would argue effort spent to fix this not worthwhile, I disagree as a CLI application should focus on basic case-insensitivity of PREFIX and COMMAND_WORDS as these are common inputs that can easily be mixed with capitalized characters knowingly or not.

---

## :question: Issue severity Team chose [`severity.VeryLow`] Originally [`severity.Low`] - [x] I disagree **Reason for disagreement:** I disagree, this is not a cosmetic issue in any way.  This is at least a FeatureFlaw by  Hence, it should be at least a `Low`.

---