You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Create a new class for SyncFrameworkIntegration, which is used for all sync framework integration (for contacts, calendars etc.) Goal is that other classes never call ContentResolver.setIsSyncable() or something like that themselves. Everything sync-framework related must be handled by this class.
The sync framework must only be used to get notified about changed content provider entries. All other users should be disabled by the new class (like current behaviour).
It should also be kept in mind that if we would ever like to change the notification of changed content provider entries to JobScheduler / WorkManager (https://github.com/bitfireAT/davx5/issues/247), it should be possible by adapting mainly this class.
The text was updated successfully, but these errors were encountered:
rfc2822
changed the title
Create a new class for SyncFrameworkIntegration, which is used for all sync framework integration (for contacts, calendars etc.) Goal is that other classes never call ContentResolver.setIsSyncable() or something like that themselves. Everything sync-framework related must be handled by this class.
[Architecture] Do sync framework integration in a separate class
Nov 1, 2024
Create a new class for
SyncFrameworkIntegration
, which is used for all sync framework integration (for contacts, calendars etc.) Goal is that other classes never callContentResolver.setIsSyncable()
or something like that themselves. Everything sync-framework related must be handled by this class.The sync framework must only be used to get notified about changed content provider entries. All other users should be disabled by the new class (like current behaviour).
It should also be kept in mind that if we would ever like to change the notification of changed content provider entries to JobScheduler / WorkManager (https://github.com/bitfireAT/davx5/issues/247), it should be possible by adapting mainly this class.
The text was updated successfully, but these errors were encountered: