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

[Feature request] Conflict resolution: ask each time #37

Closed
vatterspun opened this issue Mar 10, 2018 · 4 comments
Closed

[Feature request] Conflict resolution: ask each time #37

vatterspun opened this issue Mar 10, 2018 · 4 comments
Assignees

Comments

@vatterspun
Copy link

vatterspun commented Mar 10, 2018

(Since my "crash on launch" post was an easy fix, decided to suggest something useful instead.)

This is not high priority.

Current behavior: When I have a note that's different from the server, the options are:

image

Requested behavior: upon conflict discovery, prompt user for action. Possible question structure:

"There has been a conflict between a note in AlephNote and the synchronizing server enabled in settings." Options:

A. Take no action, display this prompt again on program restart
B. Use client version (upload and overwrite remotely)
C. Use server version (download and overwrite locally)
D. Use server version and generate backup file (note title - date-and-time.txt

@Mikescher Mikescher self-assigned this Mar 13, 2018
@vatterspun
Copy link
Author

vatterspun commented May 13, 2018

Quick note here: to be clear, I wanted to add an option to that list in the UI that says “prompt user” … I suspect most users won't need to be prompted.

Thanks.

@Mikescher
Copy link
Owner

Quick note here: to be clear, I wanted to add an option to that list in the UI that says “prompt user” … I suspect most users won't need to be prompted.

Jep, that's how I would do it.

I just have to do a few architecture changes so that the syncing can display blocking dialogs.
But it's still on my list :D

 

~ Mike

Mikescher added a commit that referenced this issue May 23, 2018
Mikescher added a commit that referenced this issue May 24, 2018
@Mikescher
Copy link
Owner

Okay the first version of the option is implemented. There are still a few things I'm not satisfied but it should work :)

@vatterspun
Copy link
Author

Okay the first version of the option is implemented. There are still a few things I'm not satisfied but it should work :)

I'm speechless. That's way above and beyond. Thumbs up.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants