Open Leofeng10 opened 2 years ago
Thanks for the issue. We accept the bug because it can be considered as a mismatch between the UG and the feature. However, we consider this as a documentation bug because when we designed the feature, we have decided to discard leading and trailing spaces in class names entered in the command box. This is consistent for all the commands. As a result, the feature itself works fine and it should not be considered a functionality bug. Rather, we recognised the UG can be clearer about this. When we state the CLASS_NAME
parameter is space sensitive, we actually mean something like Class     4E1
and Class 4E1
are treated as different class names, but not for leading/trailing spaces. Furthermore, we think it is of low severity because this is unlikely to affect teachers’ normal use of the app and only appears in rare situations: 1) users are expected to know the behaviour after only one or two trials 2) under normal situations, class names do not start or end with spaces, and a typical user will not try to add classes with such names
Team chose [type.DocumentationBug
]
Originally [type.FunctionalityBug
]
Reason for disagreement: [replace this with your explanation]
Team chose [severity.Low
]
Originally [severity.Medium
]
Reason for disagreement: [replace this with your explanation]
UG says that Class_name is space sensitive, but I cannot add the following class which name has some white space before the characters. If the Class_name is space sensitive, it should allow me to do so