351589 - No interface to update an attendee inside a calIItemBase

Status: RESOLVED WONTFIX

(Calendar :: Internal Components, defect)

Description

[cmtalbert]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.0.6) Gecko/20060728 Firefox/1.5.0.6
Build Identifier: Lightning BuildID 2006082320 Thunderbird version 3 alpha 1 20060811

You cannot update the attendee list with a new entry inside the calIItemBase interface. You would expect to have some kind of a call where you could say:
myAttendee.participationStatus= newStatus;
item.UpdateAttendee(myAttendee);

Instead, you have to do the following in order to achieve that effect:
var attendee = anItem.getAttendeeById(attendeeID);
if (attendee) {
    anItem.removeAttendee(attendee);
    attendee.participationStatus = status;
    anItem.addAttendee(attendee);
}


Reproducible: Always

Steps to Reproduce:
1. Attempt the code above and you will see the issue immediately.
This is more of a development side bug.
We should look into opening a new interface for this functionality.
Actual Results:  
You have to hack around the lack of an interface by removing and then adding the attendee. It would probably less expensive (and less hacky) to provide an update mechanism.

Expected Results:  
There will be an update mechanism for the calIItemBase attendee list.

Comment 1

[Daniel Boelzle [:dbo]]

I don't think it's worth to add API for the sketched sequence (which needs to clone the attendee object BTW) unless it's used a few times. Clint, thoughts?

Comment 2

[cmtalbert]

I agree that if it isn't used in very many places then it isn't worth it to add an API for it.  The worry when I filed this bug was that every provider that edits attendee status would be doing this, and that would be silly to force this workaround on them.  

But I think in today's codebase, these changes are handled by the iTIP Processor and not the providers, so it's ok to mark this invalid and keep the workaround in place.

--> INVALID?

Comment 3

[Daniel Boelzle [:dbo]]

or WONTFIX?

Comment 4

[Felix Möller]

I guess this should be closed ...

Comment 5

[Philipp Kewisch [:Fallen][📱📆]]

Thanks for the hint, lets close it.