Add Purple.Contact.compare and Purple.Contact.equal methods

Review Request #3693 — Created Dec. 3, 2024 and submitted

Information

pidgin/pidgin
default

Reviewers

Add Purple.Contact.compare and Purple.Contact.equal methods

Ran the unit test in valgrind.

Summary ID
Add Purple.Contact.compare and Purple.Contact.equal methods
0627e2d5078cf08c309ed6fca67210c8b7b4df1c
Description From Last Updated

why use g_object_set here instead of the actual setter?

grimgrim

ditto

grimgrim
grim
  1. 
      
  2. libpurple/tests/test_contact.c (Diff revision 1)
     
     
    Show all issues

    why use g_object_set here instead of the actual setter?

  3. libpurple/tests/test_contact.c (Diff revision 1)
     
     
    Show all issues

    ditto

    1. There's no public purple_account_set_id.

    2. Ugh that property is a mess from when account was a ContactInfo and we thought the protocol would be updating the id... But that was wrong as libpurple needs to manage it. Apparently this never got updated to be construct only which is what that probably should be.

      So, we could take this review request as is and then make that property construct only in a latter review request or adjust that here. I'm good either way and leave it up to you to decide ;)

    3. Not sure what needs to be done exactly so I'd rather leave this review request as is.

    4. Basically it'd just be updating the property flags in purple_account_class_init to use G_PARAM_CONSTRUCT_ONLY instead of G_PARAM_CONSTRUCT but then the unit tests would have to be refactored because g_object_set wouldn't work anymore.

      At any rate I'll finish reviewing this shortly and we can go from there.

  4. 
      
ivanhoe
grim
  1. Great work, thanks!!

  2. 
      
grim
Review request changed
Status:
Completed