1. 15 Nov, 2019 1 commit
  2. 20 Sep, 2019 2 commits
  3. 22 Aug, 2019 1 commit
  4. 01 Aug, 2019 1 commit
  5. 26 Jul, 2019 1 commit
    • Sébastien Blin's avatar
      refacto: remove unused LRC models · a3d9396f
      Sébastien Blin authored
      A lot of old models is now migrated to another part of the code.
      This patch removes a lot of unused models.
      
      Change-Id: I245f3c793571076ae0e5f838a672e15008152470
      Gitlab: #358
      a3d9396f
  6. 25 Jul, 2019 1 commit
  7. 18 Jul, 2019 1 commit
  8. 11 May, 2019 1 commit
  9. 06 May, 2019 2 commits
  10. 03 Jan, 2019 1 commit
  11. 11 Dec, 2018 1 commit
  12. 05 Dec, 2018 1 commit
  13. 19 Nov, 2018 1 commit
  14. 02 Oct, 2018 1 commit
  15. 20 Sep, 2018 1 commit
  16. 15 Sep, 2018 1 commit
  17. 11 Sep, 2018 1 commit
  18. 30 Aug, 2018 1 commit
  19. 29 Aug, 2018 1 commit
  20. 06 Aug, 2018 1 commit
  21. 26 Jul, 2018 1 commit
    • Sébastien Blin's avatar
      BehaviorController: add signals to notify the client for all accounts · 1e52bf86
      Sébastien Blin authored
      Currently a client got no way to listen notifications from all
      accounts at the same place and must listen for all accounts one by one.
      This patch allow clients to get notified when a call is incoming, a new
      trust request or a new interaction has arrived.
      
      Change-Id: I27790c073113d54f0adf6e2409b8e634de200d02
      1e52bf86
  22. 24 Jul, 2018 1 commit
  23. 06 Jul, 2018 2 commits
  24. 03 Jul, 2018 1 commit
  25. 05 Jun, 2018 1 commit
  26. 30 May, 2018 1 commit
  27. 22 May, 2018 1 commit
  28. 14 May, 2018 1 commit
    • Hugo Lefeuvre's avatar
      contactmodel: introduce bannedStatusChanged signal · f57ea000
      Hugo Lefeuvre authored
      cb08d760 introduced a new banned contacts logic to the contact model,
      which allows to manage banned contacts without using the old lrc.
      While this patch is fully functional, the problem of how exactly the
      client is notified about a banning / unbanning operation is still
      unclear: currently the only way the client gets notified is via the
      refreshFilter() operation. This is enough for managing banned
      contacts in the smart list, but not in the banned contacts view.
      
      In order to addres this problem we introduce a new signal,
      bannedStatusChanged, which allows the client to be notified when a
      contact is banned or unbanned.
      
      Change-Id: I2ea845e0fe311048479777504b74885cb931aa13
      Reviewed-by: Sébastien Blin's avatarSebastien Blin <sebastien.blin@savoirfairelinux.com>
      f57ea000
  29. 09 May, 2018 1 commit
    • Hugo Lefeuvre's avatar
      contactmodel: Add banned contacts logic · cb08d760
      Hugo Lefeuvre authored
      The old lrc bannedaccountmodel suffers from many issues, both in its
      design and functions. In order to be able to later remove this code,
      migrate the banned contacts logic to the contactmodel.
      
      contactmodel:
      
       - add a bannedContacts list with its mutex to store uris of banned
         contacts (not necessary but important for perfs).
       - modify addContact() to call directly addContact() (daemon side)
         when called with a banned contact. This will replace the old
         remove() method from the bannedAccountModel.
       - add a getBannedContacts method.
       - modify slotContactAdded to maintain the bannedContacts list and
         the old lrc. Also, when called with a banned contact, only refresh
         the filters, do not emit contactAdded signal.
       - modify slotContactRemoved to maintain the bannedContacts list.
       - modify addToContacts to maintain the bannedContacts list and
         update banned flags from the contactInfo.
      
      bannedcontactmodel (old lrc):
      
       - do not update daemon when remove is called since it collides with
         the contactmodel.
      
         _Using the bannedcontactmodel from old LRC for maintaining banned
         contacts is now DEPRECATED and support for this functionnality is
         planned to be dropped in a near future. Please migrate to the new
         contactmodel banned contacts features._
      
         The recommended way to unban a contact is to call addContact. This
         is symmetric to the way we ban contacts (calling removeContact).
      
      configuration manager mock:
      
       - add a synchronization mechanism to the configuration manager mock
         in order to avoid race conditions during concurrent execution of
         several removeContact / addContact functions
       - modify addContact to correctly behave if called with a banned
         contact: Instead of re-adding the contact, banned and removed
         flags should be cleared.
       - modify removeContact to use find_if instead of a for loop and
         erase contacts from the contacts list instead of simply removing
         them.
      
      tests:
      
       - add a unbanContact helper.
       - fix testPlaceCallWithBannedContact to check callId instead of
         conversation size which is pointless because invariant.
       - modify all banned contacts related tests to unban and re-check.
       - add a testBanUnbanContact test.
      
      Change-Id: I42b90559ca4baa12f0596bb927009ce6ba8b4ea3
      Reviewed-by: Sébastien Blin's avatarSebastien Blin <sebastien.blin@savoirfairelinux.com>
      cb08d760
  30. 04 May, 2018 1 commit
  31. 01 May, 2018 3 commits
  32. 30 Apr, 2018 1 commit
  33. 25 Apr, 2018 2 commits
  34. 11 Apr, 2018 1 commit