CRM-15522 make "Null" not evaluate as null if N is capitalized #79
Conversation
---------------------------------------- * CRM-15522: Last name Null disappears https://issues.civicrm.org/jira/browse/CRM-15522
|
Whoa, that is clever. :) It still scares me a little... but less scary than I was expecting... |
|
Test this please |
|
The concept of this seems OK. It hopefully goes without saying if a user enters last name as "null", then it will still be mishandled by Civi, but at least we'll handle the well-formed name "Null" properly, and we don't need to go on a wild-goose-chase for lines/use-cases that depend on the current/wonky behavior. I can't think of a case that's likely to break. It is, of course, a good idea to test inputs in a different situations (e.g. profile forms, "Edit Contact", importer). The only project I can think of that systematically manipulates case of names would be https://civicrm.org/extensions/capitalisation-corrector ( @futurefirst / @JohnFF ) but don't think there'd ever be a conflict between them. |
|
I did a quick grep for "Null" (in quotes) that didn't turn up anything (while "null" yields a lot), so I don't thiink any of the wacky places where null is saved as a string have it in proper case. |
CRM-15522 make "Null" not evaluate as null if N is capitalized Looks like we have consensus that this is safe to merge.
https://issues.civicrm.org/jira/browse/CRM-15522