I hope bugs like this eventually start an internal conversation about whether “duck typing” and trying to be smarter than potential customers of the system is actually a blessing or an evil. As a product developer/designer I know that this is a very tough problem to solve for. When I was developing three.do I was asking myself this question every time I made a design choice: do I want to assume I’m smarter than my user and try to guess what they’ve wanted to achieve there, or do I assume the user knows what they want to achieve and take their input at face value.
I understand why Coda wanted to have this logic in place: to behave in an expected way for people clueless about data types who’d just enter a date-like text value and expect it to behave as a date. I’m not entirely sure if it’s a good practice because I think it encourages ignorance. I’m sure though that the type guessing implementation is definitely flawed
P.S. @Nick_HE as a workaround, make a column
[Text sorted alphabetically].ToText() and sort on that one.
ToText() would extract the text input from any type value, strip rich text metadata if present, and return a simple text value that one can alphabetically sort on.