-
Notifications
You must be signed in to change notification settings - Fork 156
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
feat: make unsynced shares accessible #10887
Conversation
Thanks for opening this pull request! The maintainers of this repository would appreciate it if you would create a changelog item based on your changes. |
Todo: handle legacy urls |
Discussed with @tbsbdr , it's okay for the URLs to break because of the Edit: We decided to built a fallback anyway since it was easy. |
a884e47
to
ef25b0d
Compare
Makes unsynced shares accessible. The way to make this work is by using the remote item id instead of the share jail id for opening/resolving into incoming shares. In the future we should rethink the `shareId` property since the name is not really fitting anymore. `remoteItemId` would be more fitting.
ef25b0d
to
72f1be7
Compare
Renames `shareId` to `remoteItemId` and `shareRoot` to `remoteItemPath` on resources to match with the Graph terminology. Also removes the `remoteItemId` on space resources because it only matters for share spaces, in which case this is simply the space id. That means instead of blindly going for `space.remoteItemId`, it now checks if the space is actually a share space and then uses its id.
72f1be7
to
1ea70fc
Compare
1ea70fc
to
3fc1480
Compare
Quality Gate passedIssues Measures |
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.
LGTM,
we should add E2E tests for this
Agreed, I created #10931 to keep track. |
Congrats to us! 🎉 |
Description
Makes unsynced shares accessible. The way to make this work is by using the remote item id instead of the share jail id for opening/resolving into incoming shares.
Notable changes in the course of this:
shareId
toremoteItemId
andshareRoot
toremoteItemPath
on resources to match with the Graph terminology.remoteItemId
on space resources because it only matters for share spaces, in which case this is simply the space id. That means instead of blindly going forspace.remoteItemId
, it now checks if the space is actually a share space and then uses its id.Related Issue
Types of changes