Standardize behavior of non-string inputs to string expressions

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Won't Fix
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      Some string expressions such as $substr, $substrBytes, $substrCP, $strcasecmp, $toLower and $toUpper will coerce their inputs to a string, allowing numbers, code, etc. to be converted as input. Others, such as $strLenBytes and $strLenCP will only allow string inputs, resulting in an error on any other input. Still others, such as $trim, $rtrim, $ltrim, $indexOfBytes, $indexOfCP, $split, and $concat will return null on any nullish input, and only accept strings otherwise.

      We need to decide which of these behaviors is most useful and most consistent, and update the others to be consistent.

            Assignee:
            Charlie Swanson
            Reporter:
            Charlie Swanson
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: