Open jovantanyk opened 7 months ago
We agree that this is a valid issue. This issue is addressed in our DG, under planned enhancement 1.
Team chose [response.NotInScope
]
Reason for disagreement: Under Planned enhancement, it specifies changing the restrictions to allow for special characters and symbols. That is different from the issue of case sensitive names, which is a deliberate design choice as specified in the UG. While the enhancement is catered towards accounting for different languages and a wider array of names, case sensitive names are a feature flaw as they don't accurately depict the real world entity they represent; and is thus a bug and not a "feature request"
Case sensitivity: In general, case sensitivity of something should follow the case sensitivity of the real world entity it represents e.g., as person names are not case-sensitive in the real world, they shouldn't be case-sensitive in the app either. The same applies for search keywords. Incorrect case sensitivity can be considered a FeatureFlaw.
In the UG, the names of individuals are case-sensitive. This should not be the case as in the real world names are case-insensitive.
Example of Names being specified as case sensitive in add command: