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

Automatically detect sync conflicts #139

Open
OpenBagTwo opened this issue May 20, 2024 · 0 comments
Open

Automatically detect sync conflicts #139

OpenBagTwo opened this issue May 20, 2024 · 0 comments
Labels
enhancement New feature or request
Milestone

Comments

@OpenBagTwo
Copy link
Owner

OpenBagTwo commented May 20, 2024

GIVEN Steve has been careless about syncing his Ender Chests
AND has modified files within his Ender Chest on multiple systems sync his last sync

WHEN he next runs enderchest open or enderchest close between these systems

THEN EnderChest will detect when files on the destination system have been modified since the last sync[1]
AND will produce a report[2] on these conflicts
AND will ask Steve whether he would like to:

  1. Abort
  2. Proceed
  3. Selectively proceed with only folders without conflicts
  4. Selectively proceed with only specified folders[3]

SO that Steve doesn't have to manually merge the data

Notes

  1. Note that this is not simply "has newer files"—the criterion is newer than last sync time (Get timestamp of last sync #137)[3]
  2. As implied by the selectively-proceed options, this report should be per-folder (similar to the dry run report and what will be produced by Get timestep of last file changes #138)
  3. Should there be an option to keep newest, though?
  4. There should be both command-line flags and config options to disable this check or to set the default handling behavior
  5. This issue is blocked by Get timestamp of last sync #137 and Get timestep of last file changes #138
@OpenBagTwo OpenBagTwo added the enhancement New feature or request label May 20, 2024
@OpenBagTwo OpenBagTwo added this to the v0.2 milestone May 20, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant