-
-
Notifications
You must be signed in to change notification settings - Fork 84
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Don't upload event when calendar is read only #587
Don't upload event when calendar is read only #587
Conversation
2096b64
to
fbb1200
Compare
74c7d21
to
4a654f9
Compare
4a654f9
to
fbc6a96
Compare
…nt provider during populate()
4428ba7
to
7646e16
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
After having done a few changes (most important one is to get read-only in populate()
– unfortunately the ical4android API is not perfect and also not well-documented), I suggest to
- lift
LocalAddress.resetDeleted()
up toLocalResource.resetDeleted()
-
that only serves as aLocalAddress
then becomes an empty abstract classsuperclassforLocalGroup
andLocalContact
(needs to stay an interface, because it's impossible to inherit from more than one class,LocalContact
inherits already from AndroidContact) - for
LocalCalendar
, your new methodmarkAsNotDeleted()
will then overrideresetDeleted()
instead
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks, looks good and works as expected – this will save us from 403 on read-only calendars.
I'm not sure whether we really want to completely reset the local events on read-only events. It may be a valid use case to adapt the local alarm of otherwise read-only events (like it's possible with Etar).
However this could be topic of a follow-up issue/PR, as well as read-only handling of tasks.
No description provided.