we should not try to restore files/folders no longer synced because of
selective sync when detecting a data fingerprint change
in case the user deselect a folder from selective sync list, we would do
a local delete
in case the client is also detecting a change of data fingerprint (or is
stuck in restore mode) then instead of applying the new set of selected
folders to sync, it would upload unselected files/folders
Signed-off-by: Matthieu Gallien <matthieu.gallien@nextcloud.com>
As far as I'm aware local discovery can be skipped on folders that are
selective-sync blacklisted, so a local discovery is required when an
entry is removed from the blacklist.
Also rename
avoidReadFromDbOnNextSync() -> schedulePathForRemoteDiscovery()
since the old name might also imply it's not read from db in the local
discovery - which is not the case. Use Folder::
schedulePathForLocalDiscovery() for that.
