Automatically sync new calenders / task-lists

[rfc2822]

Can we easily enable it for own collections?

Discussed in #770

^{Originally posted by NextBlaubeere May 1, 2024}
I am using Nextcloud tasks quite heavily. Therefore I often create new task projects which are synced to my android phone via DAVx5.
However, everytime I create a new project i have to refresh the list on the CALDAV tab within the android app and manually select the new projects/calenders.

How can I make DAVx5 to automatically refresh the list and turn on sync for new entries?

[sunkup]

I think we should do this in two steps and in two PRs, since it really requires two changes in behaviour of the app. There are some questions to both changes that come to my mind.

PR 1. Automatic collection detection

• Should there be a setting for it? What should we call it?
• When to run the detection?
  • Before/after a sync or maybe with a periodic worker?
  • Should sync requests via sync-framework trigger the detection as well?
• Should it be turned on by default?
• When a sync triggers a refresh the "Refresh Collections" FAB becomes obsolete. Should we hide it?
• ... more ?

PR 2. Automatic sync activation

• Should there be a setting? What should we call it?
• Can we easily enable it for owned/personal collections?
• How does this work with the managed setting for pre-selecting collections for sync? See bitfireAT/davx5#111
• Should we exclude problematic collections like the nextcloud "recently contacted" collection ? See bitfireAT/davx5#111
• ... more ?

[rfc2822]

I think we should do this in two steps and in two PRs, since it really requires two changes in behaviour of the app.

Yes, I'd use this issue now only for the PR 2 as it's easier to change and already improves usability:

PR 2. Automatic sync activation

Should there be a setting? What should we call it?

I wouldn't make it a visible setting. With a safe default, there shouldn't be unexpected results.

Can we easily enable it for owned/personal collections?

I'd set it to Settings.PRESELECT_COLLECTIONS_PERSONAL for davx5-ose by default, too.

How does this work with the managed setting for pre-selecting collections for sync? See https://github.com/bitfireAT/davx5/issues/111

We already have the code :)

Should we exclude problematic collections like the nextcloud "recently contacted" collection ? See https://github.com/bitfireAT/davx5/issues/111

Yes, I'd use the same default setting to exclude the recently contacted. Other services may however also have Recently contacted folders.

@devvv4ever What do you think? Shall we enable all personal collections (CalDAV, CardDAV) (except those in the ignore-list) by default?