Open Ryan-Reno opened 2 months ago
This is a good suggestion, but this is not within the scope of v1.4, given that we had to fix more important bugs as compared to relatively minor quality of life improvements such as these. Additionally, case insensitivity is not a feature we specified in our user guide, and the app does not crash when trying to use the missing feature, as shown in the second point of this textbook screenshot.
Team chose [response.NotInScope
]
Reason for disagreement: [replace this with your explanation]
Adding two tags with different capitalizations, are apparently two different tags. This behavior was not specified anywhere in the User Guide, and it doesn't make sense for two tags with different capitalizations to be different.
Steps to reproduce: