Make first and last name available separately
AcceptedPublic

Authored by jbbgameich on Jul 21 2019, 12:26 AM.

Details

Reviewers
apol
Group Reviewers
Plasma: Mobile
Summary

Required for the Plasma Mobile phonebook app where both are separate fields

Diff Detail

Repository
R307 KPeople
Branch
master
Lint
No Linters Available
Unit
No Unit Test Coverage
Build Status
Buildable 14193
Build 14211: arc lint + arc unit
jbbgameich created this revision.Jul 21 2019, 12:26 AM
Restricted Application added a project: Frameworks. · View Herald TranscriptJul 21 2019, 12:26 AM
Restricted Application added a subscriber: kde-frameworks-devel. · View Herald Transcript
jbbgameich requested review of this revision.Jul 21 2019, 12:26 AM
apol accepted this revision.Jul 21 2019, 9:07 AM
This revision is now accepted and ready to land.Jul 21 2019, 9:07 AM
pino added a subscriber: pino.Jul 21 2019, 9:17 AM

How would first + last name work, when
a) you have multiple first names
b) you have multiple last names
c) you have only one "name" -- http://wookware.org/name.html

In case a, all first names would probably be in a string separated by spaces, same for multiple last names.
In case c, I guess only the last name would be set maybe.

I have been only working with the KContacts based vcard backend, where givenName and FamilyName could be mapped directly. I'm not quite sure what KContacts does in this cases though.

apol added a comment.Jul 21 2019, 12:11 PM
In D22599#499008, @pino wrote:

How would first + last name work, when
a) you have multiple first names
b) you have multiple last names
c) you have only one "name" -- http://wookware.org/name.html

As I see it, this is in case the user/front-end needs to treat them separately. Applications shouldn't put them together, that's why there's a separate NameProperty already.