4 ms·
I use these as labels to auto-file registrations in Gmail, and I've seen a few anti-patterns: 1. Reject at data entry even though they make me type it twice an
by Terretta 17y ago
I use these as labels to auto-file registrations in Gmail, and I've seen a few anti-patterns:
1. Reject at data entry even though they make me type it twice and they're going to do a round-trip click-to-verify. Too many to name fail this way.
2. Accept at data entry, convert it to a space (+ on URL means space). Pray that the login routine accepts an email address with a space (it probably won't). Tirerack fails this way.
3. Accept at data entry, then fail to create the account in other internal systems. Allow login using the +, but once logged in, data from internal systems is unavailable, and the portal errors in unusual ways. VMWare fails this way.
Failing using anti-pattern 1 is preferable to pattern 2 (replace with space then fail login) or 3 (accept and allow login but fail to interoperate with other systems internally).
After 45+ emails and calls about anti-pattern 3 over 18 months, VMWare still hasn't successfully delivered a VMWare license to me. By now they're on version 3 (a free upgrade if v2 was bought recently) but still haven't delivered me version 2 or 3. Next email, perhaps I should send them raganwald's article.
// EDIT: Added Tirerack.
- tptacek 17y agoThis is pretty close to an argument for writing the extra line of code to reject email addresses with "plus" characters in them: the front-end team might not know how the backend team will screw up.