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

Sequential Updates resolve to the second to last Update #32

Closed
ayumi opened this issue Jan 13, 2017 · 0 comments
Closed

Sequential Updates resolve to the second to last Update #32

ayumi opened this issue Jan 13, 2017 · 0 comments
Labels
bug
Milestone

Comments

@ayumi
Copy link
Contributor

@ayumi ayumi commented Jan 13, 2017

Repro:

  • In browser-laptop, creating a bookmark and renaming it is 2 Updates.
  • The next Sync interval, Sync resolves both Updates against the newest browser state:
    • Update 1 differs, so it's kept.
    • Update 2 is the same, so it's discarded.

Expected behavior:

  • When a resolve batch contains records with the same objectId, it should discard stale data.

Bonus:

  • browser-laptop should emit Create then Update, which would resolve to no op.
@ayumi ayumi added the bug label Jan 13, 2017
@ayumi ayumi added this to the pyramid 0 milestone Jan 13, 2017
@ayumi ayumi changed the title Bookmarking then setting a customTitle resolves to bookmark with the original title Sequential Updates resolve to the second to last Update Jan 13, 2017
@ayumi ayumi closed this in a824f43 Jan 14, 2017
ayumi added a commit that referenced this issue Jan 15, 2017
Further fix #32
ayumi added a commit that referenced this issue Jan 15, 2017
Further fix #32
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
1 participant
You can’t perform that action at this time.