diff options
author | Elvis Angelaccio <elvis.angelaccio@kde.org> | 2017-04-04 12:09:14 +0200 |
---|---|---|
committer | Elvis Angelaccio <elvis.angelaccio@kde.org> | 2017-04-04 12:13:54 +0200 |
commit | a68587718afca82a06d57cd44fc949ea547e04f6 (patch) | |
tree | 3b75fe66f6176659cf4eb6876d47fd703daf5c8c /room.cpp | |
parent | ff977a14a26076f9df426437a2049d2aefd1defc (diff) | |
download | libquotient-a68587718afca82a06d57cd44fc949ea547e04f6.tar.gz libquotient-a68587718afca82a06d57cd44fc949ea547e04f6.zip |
Don't extend the spec when calculating the display name
Room names conflicts should be handled at the client level, for example
by displaying the canonical alias in a tooltip or in the custom
delegate of the view.
If we extend the display name algorithm at the lib level, we
are just cluttering the display name in the most common scenario
(i.e. when there are no name clashes).
Diffstat (limited to 'room.cpp')
-rw-r--r-- | room.cpp | 6 |
1 files changed, 0 insertions, 6 deletions
@@ -792,12 +792,6 @@ QString Room::Private::calculateDisplayname() const // 1. Name (from m.room.name) if (!name.isEmpty()) { - // The below two lines extend the spec. They take care of the case - // when there are two rooms with the same name. - // The format is unwittingly borrowed from the email address format. - if (!canonicalAlias.isEmpty()) - return name % " <" % canonicalAlias % ">"; - return name; } |