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.

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

export skipped when file conflict is skipped #1270

Closed
wants to merge 1 commit into from

Conversation

grnd-alt
Copy link

@grnd-alt grnd-alt commented Jul 8, 2024

required by: nextcloud/server#46354

this PR will export an additional value skipped to indicate if the file conflict has been skipped rather than resolved. Before there seemed to be no way of telling the difference between skipping and selecting only the original file.

Both cases would return selected = [] and renamed = [] causing an issue in server when that skipping files would the delete the file that was moved.

@grnd-alt grnd-alt force-pushed the enh/export-skip-on-conflict-resolution branch 2 times, most recently from 6cf5496 to c6e8e7e Compare July 8, 2024 10:39
@grnd-alt grnd-alt requested review from susnux and skjnldsv July 9, 2024 07:31
Signed-off-by: grnd-alt <salimbelakkaf@outlook.de>
@AndyScherzinger AndyScherzinger force-pushed the enh/export-skip-on-conflict-resolution branch from c6e8e7e to 9d31963 Compare July 10, 2024 13:45
@susnux
Copy link
Contributor

susnux commented Jul 10, 2024

See my comment in the server PR: I do not think we need this as I think we should just skip every file where neither rename nor "new" is selected.

@grnd-alt grnd-alt closed this Jul 11, 2024
@skjnldsv skjnldsv deleted the enh/export-skip-on-conflict-resolution branch July 12, 2024 14:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants