That's my feeling as well. I don't think this should be getting past `validateFullName`, but it does currently. The trick is to ensure that `VALID_FULL_NAME_REGEXP` accounts for "wacky" so that the right error can be thrown :)