calendar.add_event can update as well about caldav HOT 5 CLOSED

I'm against any changes breaking backward compatibility

from caldav.

from caldav.

Maybe the method can be renamed, but a "deprecated" alias can be preserved for backward-compatibility?

from caldav.

I've thought a bit on it, and decided to:

• Rename the add_* to save_*, with aliases for backwards compatibility. The aliases may be removed when 1.0 is released
• Add an attribute "no_overwrite" to the save_*-methods, defaults to False. If it's True, we'll do a lookup for any existing calendar item with the same uid, and raise an error if it already exists.
• Add an attribute "no_create" to the save_*-methods, defaults to False. If it's True, we'll do a lookup for any existing calendar item with the same uid, and raise an error if it doesn't already exist.
• Also, raise an error if both no_create and no_overwrite is set to True, as this combination is invalid.

Requires some test code as well ... probably won't get around to fix this today.

from caldav.

I decided to skip the point "raise an error if both no_create and no_overwrite is set to True, as this combination is invalid". It will pass if no object is given, and otherwise anyway give an error message. I should exercise it in the tests though ...

from caldav.