Repository navigation
Conversation
Restricted entries represent folders in their original location. Folder filters and child counts must include them so navigation keeps showing them.
Drops into a restriction must use the destination folder permissions rather than those inherited by its location entry. Reuse prefetched target roles to keep listing queries constant.
Missing target metadata made accessible restricted favorites appear unavailable. Include their destination and restriction status so clients can navigate to them and evaluate drops correctly.
Use the sibling ui-kit checkout while validating its restriction confirmation dialogs in Drive before a package release.
Owners can change inherited folder access through the ui-kit confirmation dialogs. Resolve restriction entries when navigating or sharing, and refresh access lists and explorer state after the folder moves.
Restriction changes can remove the selected row or reorder its breadcrumbs. Keep the share modal mounted above those replaceable elements and give breadcrumbs stable identities so confirmation does not dismiss sharing.
A restriction points to a separate folder. Use its target identity, path and permissions for grid and sidebar drops, including move confirmation, while rejecting unavailable targets and moves into their own destination.
Keep regular and restricted folder icons visually consistent and let item titles inherit the theme color instead of forcing red.
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Allow folder owners to restrict and reopen inherited access from the sharing modal. Keep sharing open while listings, breadcrumbs and Favorites refresh, with explicit callbacks for app-specific updates.
Restricted-folder entries use the target folder’s permissions for navigation and drag-and-drop. Inaccessible folders open the denied-access preview; accessible folders keep normal navigation. Include backend target metadata and integration coverage for sharing, access, previews and moves.
Blocked on UI-kit #311: update the UI-components dependency after those APIs are released. The local UI-kit override is intentionally excluded from this PR, so the current published dependency does not yet support this branch.