Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Fix Issue #4402 : Ensure all files are synchronized when setting folder to availab… #4407

Closed
wants to merge 1 commit into from
Closed

Fix Issue #4402 : Ensure all files are synchronized when setting folder to availab… #4407

wants to merge 1 commit into from

Commits on May 20, 2024

  1. Fix: Ensure all files are synchronized when setting folder to availab… 

    …le offline

- Added a new parameter `isActionSetFolderAvailableOffline` to the `SynchronizeFileUseCase.Params` data class to handle forced synchronization when setting a folder to available offline.

- Updated `SynchronizeFileUseCase` to check for the `isActionSetFolderAvailableOffline` parameter and force a refresh of the folder's contents.

- Implemented the `forceRefresh` method to initiate a download of the file regardless of the etag comparison when `isActionSetFolderAvailableOffline` is true.

- Ensured that locally deleted files are re-downloaded if they still exist on the remote server when the parent folder is set to available offline.
- Added appropriate logging to track the synchronization process and forced refresh actions.

This fix addresses the issue where setting a folder to available offline did not correctly synchronize all its contents, especially when some files were deleted locally. Now, all files within the folder will be synchronized and set to available offline as expected.
    @praveen7512
    praveen7512 committed May 20, 2024
    Configuration menu
    Copy the full SHA
    c6d4d4d View commit details
    Browse the repository at this point in the history