Open guanyz opened 3 years ago
Reason stated in the UG. While it is acknowledged that some names may have special characters, the chosen constraints are sufficient for intended use cases.
Team chose [response.NotInScope
]
Reason for disagreement: Though this is stated as a known limitation, this still falls within the scope of the intended use case; it is intended to be used as a housing management system in a Residential College / in NUS, which can involve people with non-alphabetic characters in their name (e.g. -
is fairly common). Consider, for example, the case of bulk-adding data to the app from, say, a list of resident names; this restriction would almost certainly mess with the process and cause inconvenience, though it is entirely within the suggested use case.
It is a severity.Low
bug because it occurs rarely and causes minor inconvenience (e.g. the user must substitute the characters for spaces, or the like), but it is still a bug.
In the real world, names can have non-alphabetic characters in them. However, this is not allowed in the app.