Mailspring/spec/models
John McNair dccf4f3ad3 Parse Office 365 names (#2016)
Office 365 likes to format email addresses as follows:
Last Name, First Name (Some Description) <email@address.org>

This causes Contact.firstName() (and hence sometimes displayName()) to return
"Last Name," which looks a bit odd in the message/thread views.

The intent of the commit is to correctly parse these names so that (using the
above example):
- firstName = "First Name"
- lastName = "Last Name (Some Description)"
- fullName = "First Name Last Name (Some Description)"

These behavioral changes only impact names containing a ','.

I don't know that this really provides exhaustive coverage of Office 365, and
keeping the description as part of the last name is not completely guilt free,
but it's not any worse than the previous state of affairs which also has
the description in the same field but combined instead with (misplaced)
first name data.
2016-04-27 10:26:23 -07:00
..
category-spec.coffee fix(specs) 2016-03-14 11:22:42 -07:00
contact-spec.coffee Parse Office 365 names (#2016) 2016-04-27 10:26:23 -07:00
event-spec.coffee
file-spec.coffee
message-spec.coffee
model-spec.coffee
model-with-metadata-spec.es6
mutable-query-result-set-spec.coffee
query-range-spec.coffee
query-spec.coffee fix(db): Remove - from table names, which was a bad idea 2016-04-04 17:44:45 -07:00
query-subscription-pool-spec.coffee
query-subscription-spec.coffee fix(db-spec): Accompanying spec changes 2016-04-05 19:03:47 -07:00
thread-spec.coffee fix(sent): Do not allow sent or drafts to be modified 2016-03-10 15:44:53 -08:00