Open beaniestanley opened 3 years ago
Noted and thank you. We realise the terms used (names vs codes) can be confusing, so it is still an issue. We will specify the definitions in future. But we did not want to put too many restrictions on module names, which is why we ask for a confirmation of non-alphanumeric characters before the module name is saved, to make it more customizable for users. I hope we can agree on reducing the severity to "Very Low". Thank you!
Team chose [severity.VeryLow
]
Originally [severity.Low
]
Reason for disagreement: [replace this with your reason]
Suggestion: Instead of name of module, perhaps name it "course code" so it is clearer? Also, maybe do a check on the course code, since (I may be wrong) course codes are usually 2 alphabets followed by 4 integers and maybe a letter at the back, may I suggest to split the string to do a check whether they fulfill the criteria of a course code? Not a big issue but is good to be clear here! Especially asking for user to enter the "name" of the course, since to me, name of the module would be "Software Engineering & OOP" although stated to be "e.g. CS2113T" only when I enter an invalid info!