-
Notifications
You must be signed in to change notification settings - Fork 41
Conversation
If you want to merge this into staging, you should remove brave-syncer specific commit "Add MetaInfo to Bookmark", otherwise you can merge into brave-syncer branch |
@darkdh yes, reopened PR for brave-syncer-staging branch |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
and you should update the test
a72d29c
to
3c72f2b
Compare
88f85d3
to
e07de75
Compare
39dad93
to
23bec26
Compare
…d missing 'parentFolderObjectId':[]
Create + Update + Update of an existing object should resolve to a separate Update
23bec26
to
4af5ad4
Compare
CI failed because |
reopened PR to trigger new CI run |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why don't we have to update these two test cases?
4af5ad4#diff-dbbb41acf4ed22ffd4a6afc45647bb64R408
4af5ad4#diff-dbbb41acf4ed22ffd4a6afc45647bb64R429
…st to 'sequential Updates should become no op if the merged result equals to existingObject'
We met the situation when [CREATE, UPDATE] were merged to [CREATE], which was then ignored because local object had been existed.
This PR makes CREATE and DELETE records stays alone to prevent such ignoring. So only UPDATE records of the same object id are merged.
STR for brave-core brave-syncer branch:
Bookmarks Bar
folderExpected on DeviceA: bookmarks should be moved.