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

Syncing between Lemacs and GitHub #29

Open
ElDragonRojo opened this issue Aug 1, 2013 · 0 comments
Open

Syncing between Lemacs and GitHub #29

ElDragonRojo opened this issue Aug 1, 2013 · 0 comments

Comments

@ElDragonRojo
Copy link
Contributor

  1. Get changes from GitHub
  2. Add new items
  3. Update exiting items
    • If changes, mark as conflicted, but do not update values
  4. Push changes
    • If conflicts, notify user and cancel sync
    • If no changes, exit with success
  5. Re-start sync

Lemacs edits do not change the actual values, but are stored locally until they can be push to the truth server. The changes are applied in the next sync cycle, and possibly retained until they can be confirmed as redundant. The acutal values are updated only from the truth server, so the changes are not reflected in the local data until they are part of the truth.

If this is unnecessary caution and we can confirm the changes and apply them locally without getting them back from the server directly, we can skip this extra work.

@ghost ghost assigned ElDragonRojo Aug 1, 2013
ElDragonRojo added a commit that referenced this issue Aug 1, 2013
ElDragonRojo added a commit that referenced this issue Aug 1, 2013
* Moved all save calls to inside the success block to ensure things
happen in the right order.
* Add API to add and delete issues and comments on the GitHub server
* Implement these API, except for `deleteComment`
* Also I haven’t really tested these at all.

Refs #29
Refs #35
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

1 participant