***Note from Migration:***
Original Title was: Make the default of 'search' or 'replace' stringfunctions case insensitive instead of case sensitive to match the default of the equivalent stringsearcher/stringreplacer transformers
Today I noticed that the for the 'search' or 'replace' string functions that are discussed here, the default setting is to match 'case sensitive', where one needs to specify the optional parameter [caseSensitive] to 'FALSE' to make it match case insensitive. I thought this is a bit confusing, as the default for the equivalent transformers, i.e. the stringsearcher and the stringreplacer, are set to case insensitive.
The string functions this concerns are;
- FindRegEx(str, regExp, [startIdx], [caseSensitive], [caretMode])
- FindString(str, findStr, [startIdx], [caseSensitive])
- ReplaceRegEx(str, regExp, newStr, [caseSensitive])
- ReplaceString(str, oldStr, newStr, [caseSensitive])
Personally I prefer the default in searches to be case insensitive, so I would like it if the default of these string functions can be changed to 'case insensitive'.
However, besides my personal preferences, I think it is even more important that the case sensitivity setting of these string functions and the equivalent transformers should be consistent with each other.