Open Jasperabez opened 1 week ago
We have specified the constraints for the Student ID in the user guide to be 8 digits long for the purpose of our product. In order to fix this issue, we have to add customisability to the Student ID and the benefit of including this customisation does not outweigh the effort that it would take to implement it, given the scope of our module.
Team chose [response.NotInScope
]
Reason for disagreement: I'll argue that the effort taken to implement it is relatively trivial, is just a matter of changing the regex to allow alphabets and digits length in the parser. If the concern is that it would be overly long to enter the commands it has been shown that this wasn't a concern of the dev team in the other issue raised regarding typing the id every time for a command.
In the program, student id is limited to 8 digits. For schools that do not use this format the program would be essentially unusable for them. Example in NUS:
A0000000N
.There is no current good workaround it as there's no alternative field that could be used to fill in the id instead.
If the student id was just made to mean a shorthand to identify the student in the scope of the application it should be allowed to be variable length (less than 8 digits) to make it easier for the user to type. However this does not seems to be the case from the UG and DG.