nus-pe-bot
commented
1 year ago Team's Response
Hi, we labelled this bug as not in scope because our parameter names are meant to be a special character and unique, and it was our team's design choice to use a character that reperesents the intials of the parameter and differentiating using upper/lowercase. We chose not to use a longer parameter name since it would make the typing process more cumbersome, and we have chosen not to use another character to represent the parameters since it would be counterintuitive for the users to use.
Granted, we feel that it might be beneficial for the parameter tags to be case-insensitive since it might take additional effort to switch key-case, and it is a future enhancement that we can consider adding. However, this would be considered as a design choice, and something that would require a fundamental change.
Furthermore, should a user confuse the Deadline and description parameter names and attempt to use them, the program will let them know with an error message and will not crash.
Items for the Tester to Verify
:question: Issue response
Team chose [response.NotInScope]
- [ ] I disagree
Reason for disagreement: [replace this with your explanation]
Having prefixes with the same letter can be confusing and problematic for the user. Here you have the prefix for deadline as D and prefix for description as d