[Bug 48760] New: TpAccountManager doesn't document what its signals actually mean

[bugzilla-daemon at freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=48760

             Bug #: 48760
           Summary: TpAccountManager doesn't document what its signals
                    actually mean
    Classification: Unclassified
           Product: Telepathy
           Version: git master
          Platform: Other
        OS/Version: All
            Status: NEW
          Severity: normal
          Priority: medium
         Component: tp-glib
        AssignedTo: telepathy-bugs at lists.freedesktop.org
        ReportedBy: will.thompson at collabora.co.uk
         QAContact: telepathy-bugs at lists.freedesktop.org


>From a cursory glance at the TpAccountManager documentation, I have no idea
what signal gets emitted  when an account is added. Here are the signals:

  "account-disabled"                               : Run Last
  "account-enabled"                                : Run Last
  "account-removed"                                : Run Last
  "account-validity-changed"                       : Run Last
  "most-available-presence-changed"                : Run Last

Now I think I remember that, on the D-Bus, AccountValidityChanged is also used
to herald the arrival of a new account. So I look at its documentation to check
if I'm right:

> Emitted when the validity on account changes.
> 
> account is guaranteed to have TP_ACCOUNT_FEATURE_CORE prepared, along with
> all features previously passed to tp_simple_client_factory_add_account_features().
> 
> manager :   a TpAccountManager
> account :   a TpAccount
> valid :     TRUE if the account is now valid
> user_data : user data set when the signal handler was connected.

That's not an explanation!

-- 
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA Contact for the bug.
You are the assignee for the bug.