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

Make migrated archived items more metabasey #42963

Closed
Tracked by #38063
dpsutton opened this issue May 21, 2024 · 0 comments
Closed
Tracked by #38063

Make migrated archived items more metabasey #42963

dpsutton opened this issue May 21, 2024 · 0 comments
Assignees

Comments

@dpsutton
Copy link
Contributor

dpsutton commented May 21, 2024

Items that are migrated feel a bit hard to use. In the previous version, there was some mysterious action at hand, but it would still unarchive a tree.

OurAnalytics
└── A
    └── B
        └── C
            └── card

Example suppose collections A > B > C and in C is a card. In the archive, each of these would appear as top level in the archive, but if you unarchived B, it would unarchive C and card.

In the trash, you cannot unarchive B. If you move B, it will only move that collection and not any of it's children. Also, if you were to restore A, it would not restore any of its children.

This feels a bit more understandable. Certainly the old way was quite wild in honoring the hierarchy without showing it, i'm just worried it might be a bit too tedious.

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

No branches or pull requests

2 participants