Open LamJiuFong opened 9 months ago
Firstly, the case sensitivity portion should follow the real world entity such as the name or breed or species. However, the prefixes for the commands are not real world entity and should not be considered under having user to have more room for mistakes. Besides, making prefixes case-insensitive is only for convenience and improves quality-of-life.
Secondly, since rectifying it is also less important than the work that has been done, we decided to respond it with "NotInScope".
Team chose [response.NotInScope
]
Reason for disagreement: [replace this with your explanation]
The current implementation makes the command keywords(eg. add) and prefixes(eg. db/) case sensitive,
Maybe it is better to allow make it case-insensitive so that user can have more room for mistakes? (it is also stated in the module website)