I think User Discovery should not be case sensitive
started a topic
almost 10 years ago
It does not make sense to treat Alice and ALICE as two different users. For example, If I query with a username "ALICE", the result should contain all "Alice" (or "alice"). So in this function: [KCSUserDiscovery lookupUsersForFieldsAndValues:completionBlock:progressBlock:], lookupUsersForFieldsAndValues should not be case sensitive.