Open glenngnng opened 10 months ago
It is intended to work that way. While I agree that it can be specified, I believe it does not hinder usage at all as in real-life department names should not be case sensitive, e.g. Sales should be the same as sales.
Team chose [response.NotInScope
]
Reason for disagreement: In the course website, it states that at least one of the bellow needs to be satisfied: The UG specifies it as not supported or coming in a future version. The user cannot attempt to use the missing feature or when the user does so, the software fails gracefully, possibly with a suitable error message i.e., the software should not crash.
However, I don't think any of them are satisfied.
The UG does not specify that department is case insensitive.
will return the same result as