GIVEN Alex has messed up and made changes to files in multiple Ender Chests that haven't been synced
AND she wants to manually merge her data[1]
WHEN she runs the command enderchest status from one of her instances
THEN she gets a report such as the below:
_chest monster
16488 files
1254 directories
1 symlinks
last modified: 2024-05-19 18:14 EDT
global
93 files
19 directories
22 symlinks
last modified: 2024-05-20 13:01 EDT
...
SO she can either:
compare this report to one she gets running the command on her other machine
compare this report to an enderchest close --dry-run report
and then cross-reference the sync timestamp obtained from enderchest history (#137) [2]
AND resolve the conflict manually
Notes
[1] Using the --exclude flag, it's possible to resolve this conflict within EnderChest today, and automatically detecting these conflicts (and prompting the user to resolve them) is on the roadmap (#139)
[2] This issue is not blocked by #137
GIVEN Alex has messed up and made changes to files in multiple Ender Chests that haven't been synced AND she wants to manually merge her data[1]
WHEN she runs the command
enderchest statusfrom one of her instancesTHEN she gets a report such as the below:
SO she can either:
enderchest close --dry-runreportenderchest history(#137) [2]AND resolve the conflict manually
Notes
[1] Using the
--excludeflag, it's possible to resolve this conflict within EnderChest today, and automatically detecting these conflicts (and prompting the user to resolve them) is on the roadmap (#139) [2] This issue is not blocked by #137