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

Don't allow merging folders and livemarks #13

Merged
merged 1 commit into from
Aug 31, 2018

Conversation

linabutler
Copy link
Member

This won't go well if the folder somehow has children on one side. (Livemarks haven't had real children for a while, as seen in bug 632287, but the folder can still be modified locally). Since we're removing livemarks in bug 1477667, we can probably remove this entirely instead of adding complexity to the merger.

Copy link
Member

@mhammond mhammond left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I had a re-find my rubber stamp, but lgtm!

@mhammond
Copy link
Member

mhammond commented Aug 31, 2018

(and the fact livemarks are going away helps me be confident deploying the rubber-stamp - although I guess there will be some interesting considerations on desktop (even with the old merger) when they die.

This requires removing the entire subtree, in case we're merging a
folder with children on one side, and a livemark on the other. Since
we're removing livemarks in bug 1477667, we can remove this entirely
instead of adding complexity to the merger.
@linabutler linabutler force-pushed the folders-livemarks-incompatible branch from d602513 to 62a7b59 Compare August 31, 2018 22:33
@linabutler linabutler merged commit 62a7b59 into master Aug 31, 2018
@linabutler linabutler deleted the folders-livemarks-incompatible branch October 6, 2018 01:19
@linabutler linabutler mentioned this pull request Feb 1, 2019
3 tasks
linabutler added a commit that referenced this pull request Feb 17, 2019
For mismatched kinds, we keep both nodes with new GUIDs. This is an
edge case: Places maintenance on Desktop can change an item's
kind without changing its GUID, but this should be rare.

In general, we can't meaningfully pick a side when two items have
different kinds (a bookmark and a folder with children? a bookmark and
a separator?), so we keep both, with new structure, to avoid possible
data loss.

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

Successfully merging this pull request may close these issues.

None yet

2 participants