Open Bug 328617 Opened 19 years ago Updated 3 years ago

calICalendars.getCalendars needs better error-semantics

Categories

(Calendar :: Internal Components, defect)

defect

Tracking

(Not tracked)

People

(Reporter: dmosedale, Unassigned)

References

Details

If there is an error while getting one of the calendars in calCalendarManager.getCalendars() the error is ignored (though there may well be traces in the JS console), and an incomplete list of calendars is returned, but the caller gets no indication that this has happened. calICalendarManager is intended to be callable from arbitrary code (eg sync conduits), so it shouldnt be assuming that it can just prompt the user about this. Instead, we need to have more complete semantics for communicating what happened to the caller. One conceivable way to do this might be to have an "error-calendar" provider which has one pseudo-calendar for each calendar creation that fails containing more info about the failure. This seems like a sort of strange solution, though. It would probably be cleaner to define an exception type array and return an array of such exceptions. Weve talked about defining more useful calendar exception type before, which I think we want to do anyway. I dont think theres a bug filed about that yet, but I could be wrong.
See also bug 313624 and bug 313627, which are somewhat related.
Blocks: 328618
The bugspam monkeys have struck again. They are currently chewing on default assignees for Calendar. Be afraid for your sanity!
Assignee: base → nobody
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.