soc-se-bot
commented
3 months ago Team's Response
This is actually caused by the fact that the app requires exactly the same case as what was specified in the UG for the MAJOR_NAME the first time each of the majors are used. It is not a difference between init and display.
This issue is a duplicate of another issue.
The 'Original' Bug
[The team marked this bug as a duplicate of the following bug]
inconsistency in handling init MAJOR_NAME
Inconsistency how the init command handles case sensitivity for major codes in the PlaNUS application. Initially, init ceg and init ee are not accepted (first time entering), prompting the user to retry with a major code, implying that uppercase should be used. However, upon re-entering init EE in uppercase, the subsequent attempt with init ee in lowercase seems to be accepted without an error
[original: nus-cs2113-AY2324S2/pe-interim#1202] [original labels: severity.Low type.FunctionalityBug]
Their Response to the 'Original' Bug
[This is the team's response to the above 'original' bug]
Thank you
Items for the Tester to Verify
:question: Issue duplicate status
Team chose to mark this issue as a duplicate of another issue (as explained in the Team's response above)
- [ ] I disagree
Reason for disagreement: [replace this with your explanation]
Inconsistency in the way the application handles MAJOR_NAME for init function it only accepts uppercase e.g. CEG not ceg but for display function it accepts both upper and lower case e.g. CEG and ceg which can be confusing for users based on the UG which states that both display and init uses the same MAJOR_NAME