Open charlesliyifeng opened 1 week ago
Thank you for pointing this out and for your valuable feedback. While we understand that specifying whether the NAME field is case-sensitive in the User Guide (UG) and Developer Guide (DG) may add clarity, this issue falls outside the intended scope of the documentation for the following reasons:
The application’s behaviour regarding case sensitivity is consistent across all features that involve the NAME field. Users can reasonably expect the same behaviour to apply universally, based on their interaction with the app. Since this consistency is inherent to the design, we prioritised simplicity in the documentation by omitting repetitive details.
Team chose [response.NotInScope
]
Reason for disagreement: [replace this with your explanation]
It would be better for the user if they can know this from reading the UG, instead of testing the product by themselves to find out.
This information is also not found anywhere in in-app error messages or help.