Open UnwilledTangent opened 1 year ago
Not a documentation bug. Accepting inputs like "malE" allows our app to be more robust in accepting minor errors in user input so as to improve user friendliness.
Team chose [response.Rejected
]
Reason for disagreement: If your team chooses to allow inputs like "malE", then your User Guide should be reflected as follows, "male or m or female or f (not case sensitive)".
Choosing to say only "male or m or female or f" will cause some misunderstanding, as the user might think that he/she can only input "male or m or female or f", not "malE".
This is wrong, because the field Gender can accept "malE". I would recommend changing the code instead of the UG tho.