Skip to content

fix: get by shared folder name returns full data#1914

Merged
sshrushanth-ks merged 1 commit intoget-share-folder-fixfrom
get-share-folder-fix-int
Apr 2, 2026
Merged

fix: get by shared folder name returns full data#1914
sshrushanth-ks merged 1 commit intoget-share-folder-fixfrom
get-share-folder-fix-int

Conversation

@sshrushanth-ks
Copy link
Copy Markdown
Contributor

When using get <name> on a shared folder, the name resolution path now delegates to the UID-based execution path via self.execute(), ensuring users, teams, and share_admins are included in the output instead of only basic folder fields.

…When using `get <name>` on a shared folder, the name resolution path now delegates to the UID-based execution path via `self.execute()`, ensuring users, teams, and share_admins are included in the output instead of only basic folder fields.
@sshrushanth-ks sshrushanth-ks merged commit 04f2cb3 into get-share-folder-fix Apr 2, 2026
4 checks passed
sshrushanth-ks added a commit that referenced this pull request Apr 7, 2026
…When using `get <name>` on a shared folder, the name resolution path now delegates to the UID-based execution path via `self.execute()`, ensuring users, teams, and share_admins are included in the output instead of only basic folder fields. (#1914)
sshrushanth-ks added a commit that referenced this pull request Apr 9, 2026
…When using `get <name>` on a shared folder, the name resolution path now delegates to the UID-based execution path via `self.execute()`, ensuring users, teams, and share_admins are included in the output instead of only basic folder fields. (#1914)
sk-keeper pushed a commit that referenced this pull request Apr 9, 2026
…When using `get <name>` on a shared folder, the name resolution path now delegates to the UID-based execution path via `self.execute()`, ensuring users, teams, and share_admins are included in the output instead of only basic folder fields. (#1914)
sk-keeper pushed a commit that referenced this pull request Apr 9, 2026
…When using `get <name>` on a shared folder, the name resolution path now delegates to the UID-based execution path via `self.execute()`, ensuring users, teams, and share_admins are included in the output instead of only basic folder fields. (#1914)
@sshrushanth-ks sshrushanth-ks deleted the get-share-folder-fix-int branch April 16, 2026 10:07
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.

4 participants