feat(move): add received sharing destinations - #4208
doubleface wants to merge 6 commits into
Conversation
|
Important Review skippedAuto reviews are disabled on base/target branches other than the default branch. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Advanced Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
BundleMonFiles updated (2)
Unchanged files (14)
Total files change -343B -0.06% Groups updated (2)
Unchanged groups (1)
Final result: ✅ View report in BundleMon website ➡️ |
95f17ca to
bb662f9
Compare
6c9e9c5 to
ecfca55
Compare
Handle MoveTo navigation and query refreshes for Shared Drive and Nextcloud sources. Keep the viewer open when the dialog is cancelled and leave it after a successful move. Add end-to-end coverage for moving a Shared Drive file from the viewer.
ecfca55 to
d4fe213
Compare
Expose the Sharing section in Move to and preserve federated sharing context for permission checks, folder creation, and confirmation.
Exercise file and folder moves into editor sharings and verify that viewer sharings remain unavailable as destinations.
Cover moves between federated shared drives and pending query state.\nRoute sharing setup through authenticated fixtures and page objects.\nKeep the file picker tabs aligned with their folder contents.\n\nValidated with the targeted Playwright suite (5 tests).
Public move contexts do not expose authenticated sharing paths, so the force calculation crashed before any move request was sent. Skip the shared-path lookup for public moves and cover the editable public-link flow with unit and end-to-end tests. Validated with the targeted MoveModal suite and the public-link Playwright scenario.
Cover the mobile MoveTo flow and total move failures with retry. Generalize the Playwright mobile project so every mobile spec runs on the device profile. Validated with the focused mobile suite and the desktop MoveTo, received-sharing, and Shared Drive scenarios.
ccff8c3 to
c446467
Compare
There was a problem hiding this comment.
Gates Passed
3 Quality Gates Passed
See analysis details in CodeScene
Quality Gate Profile: The Bare Minimum
Install CodeScene MCP: safeguard and uplift AI-generated code. Catch issues early with our IDE extension and CLI tool.
| const addedItems = additionalItems.filter( | ||
| item => | ||
| item?.dir_id === folderId && | ||
| item.driveId === driveId && |
There was a problem hiding this comment.
Will remove unneeded optional chaining in new PR which will not come from a fork
| item?.dir_id === folderId && | ||
| item.driveId === driveId && | ||
| !sourceIds.has(item._id ?? item.id) | ||
| ) |
There was a problem hiding this comment.
Why do we have two source for items?
There was a problem hiding this comment.
One source is data coming from server and the other contains data created locally, waiting from server update (optimistic data). I will clarify this with a better naming
|
Thanks for the multiple commits |
|
@doubleface why this PR is from a fork? |
dcd6be6 to
17025a4
Compare
Summary
fixes #4175